From: prashantv <prashant.is.here@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Re[2]: Slow fork issue - Win x64
Date: Tue, 20 Jan 2009 13:51:00 -0000 [thread overview]
Message-ID: <21561482.post@talk.nabble.com> (raw)
In-Reply-To: <1542859895.20080918134643@F1-Photo.com>
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://www.nabble.com/Slow-fork-issue---Win-x64-tp19538601p21561482.html
Sent from the Cygwin list mailing list archive at Nabble.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/
next prev parent reply other threads:[~2009-01-20 11:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1221716111.21095.ezmlm@cygwin.com>
2008-09-18 11:47 ` Jay
2008-09-18 15:23 ` Re[2]: " Paul-Kenji Cahier
2009-01-20 13:51 ` prashantv [this message]
2010-02-16 12:19 ` Jarkko Häkkinen
2010-02-18 0:15 ` Cyrille Lefevre
2010-02-18 21:20 ` Jarkko Häkkinen
2010-10-10 19:38 ` Re[2]: " Nicole Hamilton
2010-10-11 18:16 ` Reini Urban
2010-10-11 19:11 ` Nicole Hamilton
2008-09-18 3:23 Paul-Kenji Cahier
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=21561482.post@talk.nabble.com \
--to=prashant.is.here@gmail.com \
--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).