| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-Spam-Check-By: | sourceware.org |
| Date: | Wed, 17 Sep 2008 20:41:40 +0200 |
| From: | Paul-Kenji Cahier <pkc AT F1-Photo DOT com> |
| X-Mailer: | The Bat! (v4.0.16.2) Professional |
| Reply-To: | Paul-Kenji Cahier <pkc AT F1-Photo DOT com> |
| Message-ID: | <1613876000.20080917204140@F1-Photo.com> |
| To: | cygwin AT cygwin DOT com |
| Subject: | Slow fork issue - Win x64 |
| MIME-Version: | 1.0 |
| X-IsSubscribed: | yes |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Id: | <cygwin.cygwin.com> |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
| Sender: | cygwin-owner AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| Delivered-To: | mailing list cygwin AT cygwin DOT com |
Hello,
I have been noticing extreme slowdowns in vista/2k8 64 with latest cygwin 1.5.
Fresh installation, no antivirus.
The command used to test speed is:
while (true); do date; done | uniq -c
On windows 2008 64bit:
11 Wed Sep 17 20:35:22 RDT 2008
11 Wed Sep 17 20:35:23 RDT 2008
12 Wed Sep 17 20:35:24 RDT 2008
11 Wed Sep 17 20:35:25 RDT 2008
12 Wed Sep 17 20:35:26 RDT 2008
11 Wed Sep 17 20:35:27 RDT 2008
12 Wed Sep 17 20:35:28 RDT 2008
11 Wed Sep 17 20:35:29 RDT 2008
11 Wed Sep 17 20:35:30 RDT 2008
On windows XP SP3 32bit:
51 Wed Sep 17 20:35:42 2008
50 Wed Sep 17 20:35:43 2008
50 Wed Sep 17 20:35:44 2008
51 Wed Sep 17 20:35:45 2008
50 Wed Sep 17 20:35:46 2008
51 Wed Sep 17 20:35:47 2008
48 Wed Sep 17 20:35:48 2008
50 Wed Sep 17 20:35:49 2008
50 Wed Sep 17 20:35:50 2008
I of course wont compare to linux since the situation is quite different(and cygwin's fork
has a lot more work to do)
At first I thought it was a syswow64(windows on windows 64, the windows 32 subsystem of windows 64bit)
that was causing the issue since cygwin is 32 bit.
But then I ran the following test:
Running 200 times the 32bit cmd.exe /C exit from cygwin and from a normal 32bit windows cmd.
To my great surprise cygwin took 14seconds, while cmd took 2.5seconds.
The only difference I can see between the two is that cygwin's fork does more work...
But should it really be such a big difference?
Thanks for any hints,
--
Best regards,
Paul-Kenji mailto:pkc AT F1-Photo DOT com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |