public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "David E. Weekly" <david@there.com>
To: "cygwin" <cygwin@cygwin.com>
Subject: Cygwin is SLOW.
Date: Tue, 16 Jul 2002 03:25:00 -0000	[thread overview]
Message-ID: <LHEEIFOFMFKJEJHIKLJCGENECEAA.david@there.com> (raw)

Modern cygwins seem to be very slow. "Modern" meaning built within the last
6 months or so, and "slow" means that many basic file operations, such as
"chmod", seem to be >10x slower (measured, not exaggerating) than previous
cygwins. This is creating a pretty tight situation at our company as we're
having to rewrite scripts, etc, to work around this. The sample test script
below should demonstrate the problem. With "old" cygwins I got nearly 1000
chmod's second on my workstation. With "new" cygwins I get under a dozen.
The comparison was done on the same machine, same filesystem (NTFS) with
otherwise identical conditions.

Have others been running into this? We're seeing this on all the machines at
our company, so I'm pretty convinced it's not just a localized wierdness or
misconfiguration. We'd love to be using Cygwin, but we may have to bail if
we can't get it to run acceptably fast.

-david


=====================================


chmod ( 000, "test.file" ) || die "chmod test.file: $!";
-w "test.file" || die "cannot change test.file's permissions" $!";
$t = time;
while( $t == time ) {}
$t = time;
$secs = 5;
$stop = $t + $secs;
while( time < $stop ) {
  system( "chmod 777 test.file" ) == 0 or die "blah, $!";
  $n++;
}
print $n / $secs, " chmods per sec\n";
-w "test.file" || die "test.file is not writeable: $!";


--
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/

             reply	other threads:[~2002-07-16  6:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16  3:25 David E. Weekly [this message]
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
2002-07-16  3:48 John Vincent
2002-07-16 11:42 BiDuS
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

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=LHEEIFOFMFKJEJHIKLJCGENECEAA.david@there.com \
    --to=david@there.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).