From: Mumit Khan <khan@NanoTech.Wisc.EDU>
To: cygwin@cygwin.com
Subject: Re: Optimizing away "ReadFile" calls when Make calls stat()
Date: Tue, 13 Feb 2001 13:50:00 -0000 [thread overview]
Message-ID: <Pine.HPP.3.96.1010213154656.15708F-100000@hp2.xraylith.wisc.edu> (raw)
In-Reply-To: <4.3.1.2.20010213154412.04990ba0@pop.ma.ultranet.com>
On Tue, 13 Feb 2001, Larry Hall (RFK Partners, Inc) wrote:
> At 03:25 PM 2/13/2001, DJ Delorie wrote:
> >
> >Actually, it is. I did some benchmarks using the native Win32 API
> >directly, and Linux is way faster.
>
>
> Any chance that you have a pointer to the results of such a test? Just
> curious.
And I have seen results that show W2k/NTFS_5 to be at least as fast as
some of the Unix counterparts, and I trust neither (at least not w/out
more information). I also don't trust benchmark numbers of Linux/ext2fs,
because of the metadata issue, nor do I trust some of the other Unix and
W2k numbers because of other issues. *BSD and Linux folks don't believe
each others numbers either. Argh, Just can't win. Skeptical crisis all
over again.
Regards,
Mumit
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2001-02-13 13:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Christopher Faylor
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: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 [this message]
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
2001-02-13 14:15 Puttkammer, Roman
2001-02-13 14:28 ` Christopher Faylor
2001-02-14 2:41 Bernard Dautrevaux
2001-02-14 4:46 Bernard Dautrevaux
2001-02-16 9:24 Bernard Dautrevaux
2001-02-16 10:17 ` 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=Pine.HPP.3.96.1010213154656.15708F-100000@hp2.xraylith.wisc.edu \
--to=khan@nanotech.wisc.edu \
--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).