This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Re[2]: Slow fork issue - Win x64
- From: Jarkko HÃkkinen <jarkko dot hakkinen at hotmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 16 Feb 2010 04:19:25 -0800 (PST)
- Subject: Re: Re[2]: Slow fork issue - Win x64
- References: <1613876000.20080917204140@F1-Photo.com> <COL101-W1796553906F07DD5A0E579E64F0@phx.gbl> <1542859895.20080918134643@F1-Photo.com> <21561482.post@talk.nabble.com>
I'm getting rather similar results on my Cygwin 1.7.1, Windows 7 as evidenced
by the figures below. Upgraded from a dual core Windows XP to a quad core i7
Windows 7 causing my cygwin performance to plummet. Even the bash
auto-completion is so annoyingly sluggish that it makes the shell virtually
unusable.
For me, there's no choice between whether or not to make the transition from
XP to 7 as we're using the latest DirectX technology. Hope somebody will
figure this out.
[13:41:50 ~]$ while (true); do date; done | uniq -c
5 Tue Feb 16 14:00:09 FLEST 2010
7 Tue Feb 16 14:00:10 FLEST 2010
9 Tue Feb 16 14:00:11 FLEST 2010
9 Tue Feb 16 14:00:12 FLEST 2010
9 Tue Feb 16 14:00:13 FLEST 2010
9 Tue Feb 16 14:00:14 FLEST 2010
9 Tue Feb 16 14:00:15 FLEST 2010
9 Tue Feb 16 14:00:16 FLEST 2010
6 Tue Feb 16 14:00:17 FLEST 2010
5 Tue Feb 16 14:00:18 FLEST 2010
9 Tue Feb 16 14:00:19 FLEST 2010
prashantv wrote:
>
> My speeds are even slower than those posted:
>
> Prashant@HOME [~]
> $ while (true); do date; done | uniq -c
> 1 Tue Jan 20 22:25:50 AUSEDT 2009
> 1 Tue Jan 20 22:25:51 AUSEDT 2009
> 2 Tue Jan 20 22:25:52 AUSEDT 2009
> 1 Tue Jan 20 22:25:53 AUSEDT 2009
> 2 Tue Jan 20 22:25:54 AUSEDT 2009
> 2 Tue Jan 20 22:25:55 AUSEDT 2009
> 1 Tue Jan 20 22:25:56 AUSEDT 2009
> 3 Tue Jan 20 22:25:57 AUSEDT 2009
> 1 Tue Jan 20 22:25:58 AUSEDT 2009
> 2 Tue Jan 20 22:25:59 AUSEDT 2009
> 2 Tue Jan 20 22:26:00 AUSEDT 2009
> 2 Tue Jan 20 22:26:01 AUSEDT 2009
>
> I am running cygwin 1.5.25, Windows 2008 x64 on a Intel Core 2 @ 2.13ghz.
> One CPU is maxed to 100% when forking. This speed explained why opening
> bash took as long as 10 seconds, and I wanted to find out why it was so
> slow.
>
> Is it possible to profile the implementation easily?
>
--
View this message in context: http://old.nabble.com/Slow-fork-issue---Win-x64-tp19538601p27607447.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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