From: Michael Ludwig <milu71@gmx.de>
To: cygwin@cygwin.com
Subject: Re: Slowdown after update on Win32 (XP Home)
Date: Sat, 30 Oct 2010 14:41:00 -0000 [thread overview]
Message-ID: <20101030135525.GQ2436@wladimir> (raw)
In-Reply-To: <20101006222706.GJ3984@wladimir>
Michael Ludwig schrieb am 07.10.2010 um 00:27 (+0200):
> SZABÃ Gergely schrieb am 06.10.2010 um 23:30 (+0200):
> >
> > please see this thread (test scripts included):
> > http://cygwin.com/ml/cygwin/2010-09/msg00871.html
>
> Thanks, Gabor - I saw your thread, which reinforces my belief that it
> is a Cygwin issue.
I don't think any more the slow process creation (fork) I'm seeing is a
Cygwin problem. A Makefile for ActiveState Perl also takes an eternity
to run. The delay appears to be caused by time-consuming process
creation.
> > I can only confirm this. Process creation is much slower with 1.7.7
> > than it was with 1.5.25. The "fork" script runs 300% slower on my XP
> > box.
>
> Another possibility would be a recent Microsoft update.
>
> Am I hallucinating when I think that 100% true Windows utilities like
> IPCONFIG, ROUTE and NET are also slower in launching?
These Windows utilities also take time to launch. All processes, once
running, do *not* appear slow; they just take time to get started.
What can I do at the Windows or Cygwin level to find the cause of this
slowdown?
--
Michael Ludwig
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2010-10-30 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100930231948.GA792@wladimir>
2010-10-01 0:38 ` Larry Hall (Cygwin)
2010-10-02 0:09 ` Michael Ludwig
2010-10-04 0:50 ` Larry Hall (Cygwin)
2010-10-06 18:59 ` Michael Ludwig
2010-10-06 21:31 ` SZABÓ Gergely
2010-10-06 22:27 ` Michael Ludwig
2010-10-06 22:42 ` Michael Ludwig
2010-10-30 14:41 ` Michael Ludwig [this message]
2010-12-13 10:01 ` Michael Ludwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101030135525.GQ2436@wladimir \
--to=milu71@gmx.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).