From: Vincent Richomme <forumer@smartmobili.com>
To: David Morgan <dmorgan@aechelon.com>
Cc: <cygwin@cygwin.com>
Subject: Re: Cygwin slow on x64 systems
Date: Sun, 24 Jan 2010 02:22:00 -0000 [thread overview]
Message-ID: <1847a1f034b137ba0d95d8a866bfc070@mail.smartmobili.com> (raw)
In-Reply-To: <20100123171936.GE23796@err>
On Sat, 23 Jan 2010 11:19:36 -0600, David Morgan <dmorgan@aechelon.com>
wrote:
> Hello all,
>
> We use cygwin for our build environment, and have observed that
> everything runs extremely slow on x64 systems, for versions newer than
> approximately 1.5.12 (including 1.7.1). When I run the following
command
> in BASH,
>
> while true; do date >> file; done
>
> on a 1.5.12 Core II system, I get approximately 100 dates per second.
> On a 1.7.1 Nehalem system, I get approximately 15, and it takes several
> seconds for Ctrl-C to take effect, whereas it's instantaneous on 1.5.12.
> It makes no difference whether I redirect the output or not.
>
> We have found that the problem was introduced somewhere between 1.5.12
> and 1.5.24-2. We have not seen any such slowdown on x86 systems.
> We have observed this on XP x64, Server 2003 R2 x64, and now (with 1.7.1
> only) on Windows 7 x64.
>
> Can anyone recommend how we could profile this to help isolate the
problem?
> We have vTune and Quantify in-house.
Hope you will find something because I already have reported this but with
no success.
My QuadCore 3.GHz with 4GB feels like an old 386 when running cygwin on
Windows 7 64 bits!
--
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-01-23 23:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 22:32 David Morgan
2010-01-24 2:22 ` Vincent Richomme [this message]
2010-04-25 2:41 ` StephenBartlett
2010-04-30 2:37 ` greenup greenup
2010-04-30 3:06 ` NightStrike
2010-04-30 13:58 ` Edward Lam
2010-04-30 15:24 ` Christopher Faylor
2010-08-30 11:23 Sagi Ben-Akiva
2010-08-30 14:26 ` Edward Lam
2010-08-30 16:53 ` Edward Lam
2010-08-31 13:04 ` Sagi Ben-Akiva
2010-08-31 21:36 ` Magnus Holmgren
2010-09-01 17:12 ` Magnus Holmgren
2010-09-01 17:15 ` Eric Blake
2010-09-01 17:27 ` Magnus Holmgren
2010-09-01 17:30 ` Eric Blake
2010-09-01 18:31 ` Daniel Colascione
2010-09-06 11:32 ` Sagi Ben-Akiva
2010-09-06 17:36 ` Christopher Faylor
2010-09-06 17:51 ` Sagi Ben-Akiva
2010-09-01 18:37 ` Christopher Faylor
2010-09-01 19:00 ` Edward Lam
2010-09-01 19:10 ` Christopher Faylor
2010-09-01 20:19 ` Heath Kehoe
2010-09-01 21:21 ` Christopher Faylor
2010-09-02 3:28 ` Yaakov (Cygwin/X)
2010-09-02 5:11 ` Christopher Faylor
2010-09-07 6:12 ` Christopher Faylor
2010-09-07 7:42 ` Christopher Faylor
2010-09-08 15:13 ` Christopher Faylor
2010-09-20 8:55 ` Christopher Faylor
2010-09-20 9:40 ` Yaakov (Cygwin/X)
2010-09-20 9:41 ` Christopher Faylor
2010-09-26 17:38 ` Yaakov (Cygwin/X)
2010-09-26 18:10 ` Christopher Faylor
2010-09-27 1:19 ` Yaakov (Cygwin/X)
2010-09-27 1:36 ` Christopher Faylor
2010-08-31 7:18 Roland Schwingel
2010-08-31 14:19 ` Christopher Faylor
2010-08-31 15:12 ` Edward Lam
2010-08-31 16:48 ` Christopher Faylor
2010-08-31 17:41 ` Magnus Holmgren
2010-08-31 19:23 ` Christopher Faylor
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=1847a1f034b137ba0d95d8a866bfc070@mail.smartmobili.com \
--to=forumer@smartmobili.com \
--cc=cygwin@cygwin.com \
--cc=dmorgan@aechelon.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).