From: "Puttkammer, Roman" <roman.puttkammer@multex.com>
To: cygwin@cygwin.com
Subject: RE: Optimizing away "ReadFile" calls when Make calls stat()
Date: Tue, 13 Feb 2001 14:15:00 -0000 [thread overview]
Message-ID: <2CB1272B2212D211974D00805FCB57420AFAFCE1@mxmail.multex.com> (raw)
> -----Original Message-----
> From: jfaith@lineo.com [ mailto:jfaith@lineo.com ]
> ...
> script just did "make --version > /dev/null" one thousand times
> ...
> Linux: 3 sec.
> VMWare running Linux: 9 sec.
> DOS (batch file) 18 sec.
> Cygwin: 30 sec.
AFAIK, fork() tends to be much slower on windows than on most unixes
such as solaris or linux. Hence you'll always get a bad performance
on windows when running this kind of tests. I doubt however that you
can generalize these results; it's kind of like comparing pineapples
with carrots.
The reason why this is the case though is probably because unixes are
optimized for server applications using many heavy and light weight
processes/threads. Windows however seems to be optimized for running
10meg VB script functions inside an excel spreadsheet - and it does
actually a pretty good job running those :-)
putt
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2001-02-13 14:15 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 14:15 Puttkammer, Roman [this message]
2001-02-13 14:28 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 9:24 Bernard Dautrevaux
2001-02-16 10:17 ` Christopher Faylor
2001-02-14 4:46 Bernard Dautrevaux
2001-02-14 2:41 Bernard Dautrevaux
2001-02-13 10:36 Jonathan Kamens
2001-02-13 10:56 ` Larry Hall (RFK Partners, Inc)
2001-02-13 11:01 ` jik-cygwin
2001-02-13 11:14 ` Larry Hall (RFK Partners, Inc)
2001-02-13 11:18 ` jik-cygwin
2001-02-13 11:26 ` Larry Hall (RFK Partners, Inc)
2001-02-13 11:35 ` DJ Delorie
2001-02-13 11:46 ` jik-cygwin
2001-02-13 11:54 ` DJ Delorie
2001-02-13 11:56 ` Jonathan Kamens
2001-02-13 12:06 ` DJ Delorie
2001-02-13 12:31 ` Larry Hall (RFK Partners, Inc)
2001-02-13 12:22 ` Christopher Faylor
2001-02-13 12:50 ` DJ Delorie
2001-02-14 0:12 ` Egor Duda
2001-02-14 0:17 ` Robert Collins
2001-02-15 11:47 ` Warren Young
2001-02-15 13:14 ` Larry Hall (RFK Partners, Inc)
2001-02-15 14:17 ` Charles S. Wilson
2001-02-16 1:34 ` Warren Young
2001-02-16 8:07 ` Larry Hall (RFK Partners, Inc)
2001-02-16 9:00 ` Christopher Faylor
2001-02-15 14:17 ` Christopher Faylor
2001-02-15 14:19 ` Jonathan Kamens
2001-02-16 1:14 ` Egor Duda
2001-02-16 1:29 ` Warren Young
2001-02-13 15:28 ` Warren Young
2001-02-14 0:48 ` Lothan
2001-02-13 11:12 ` Earnie Boyd
2001-02-13 11:46 ` Christopher Faylor
2001-02-13 11:09 ` Earnie Boyd
2001-02-13 11:15 ` jik-cygwin
2001-02-13 11:48 ` Earnie Boyd
2001-02-13 11:54 ` jik-cygwin
2001-02-13 12:25 ` DJ Delorie
2001-02-13 12:50 ` Larry Hall (RFK Partners, Inc)
2001-02-13 12:51 ` DJ Delorie
2001-02-13 13:37 ` jfaith
2001-02-13 13:50 ` Mumit Khan
2001-02-13 14:13 ` DJ Delorie
2001-02-13 12:11 ` DJ Delorie
2001-02-13 11:24 ` Eric M. Monsler
2001-02-13 11:28 ` jik-cygwin
2001-02-13 12:04 ` Eric M. Monsler
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=2CB1272B2212D211974D00805FCB57420AFAFCE1@mxmail.multex.com \
--to=roman.puttkammer@multex.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).