From: "BiDuS" <bidus@free.fr>
To: <cygwin@cygwin.com>
Subject: RE: Cygwin is SLOW
Date: Tue, 16 Jul 2002 11:42:00 -0000 [thread overview]
Message-ID: <023601c22ce2$48b5cbe0$a50aa8c0@pcse5> (raw)
I've tried both slow and fast perl scripts on my machine (AMD XP1700, W2K)
If test.file is on a local directory
$ perl slowchm.pl
113.4 chmods per sec
$ perl fastchm.pl
2923.6 chmods per sec
if test.file is on a mounted directory
$ perl slowchm.pl
51.9 chmods per sec
$ perl fastchm.pl
143 chmods per sec
Could anyone explain the performance ratio for both scripts ???
btw, on a "slow" linux p3-866
test.file being on a remote directory
$ perl slowchm.pl
187.8 chmods per sec
$ perl fastchm.pl
3096.8 chmods per sec
test.file being on a local directory
$ perl slowchm.pl
181.7 chmods per sec
$ perl fastchm.pl
263232.5 chmods per sec (arf!)
I got a wider gap for small c program opening and closing about 650 files
It takes 0.750 s for local files and about 2 s for distant files
On the linux machine, it's just 0.1 s for distant files...
Is the _open() routine guilty ?
Is it linked to the unix AND dos path compatibility ?
Anyone as a hint to speed this up ?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-07-16 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 11:42 BiDuS [this message]
2002-07-16 13:39 ` Bernard A Badger
2002-07-17 7:01 ` Tony Arnold
[not found] <1026851730.8871.ezmlm@cygwin.com>
2002-07-17 3:09 ` BiDuS
2002-07-17 7:18 ` Bernard A Badger
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 3:48 John Vincent
2002-07-16 3:25 David E. Weekly
2002-07-16 8:20 ` Bernard A Badger
2002-07-16 8:31 ` Bernard A Badger
2002-07-16 8:38 ` Joe Buehler
2002-07-16 8:44 ` Bernard A Badger
2002-07-16 15:54 ` David E. Weekly
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='023601c22ce2$48b5cbe0$a50aa8c0@pcse5' \
--to=bidus@free.fr \
--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).