public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Scott Blachowicz <scott@sabami.seaslug.org>
To: cygwin@sourceware.cygnus.com
Subject: Re: Cygwin performance (was [ANN] PW32 the...)
Date: Tue, 14 Mar 2000 16:29:00 -0000	[thread overview]
Message-ID: <19940315002847.279871F1B@sabami.seaslug.org> (raw)
In-Reply-To: <20000313180831.I8690@cygnus.com>

Geoffrey Noer <noer@cygnus.com> wrote:

> ...
> Interesting. We have been trying to improve (and succeeding in improving)
> Cygwin's runtime performance but that's been done comparing Cygwin to
> Cygwin-past and not so much by doing benchmarks against other systems I
> think.

Great! Have you found any way to improve the performance of commands like 'ls'
against remotely mounted file systems? I frequently have things like

 NET USE * \\SERVER\SHARE

where SERVER is located on the far end of a PPTP link to a system a few
thousand miles (18-22 hops over the Internet via an ISDN connection on my end)
and doing an 'ls' is unuseably slow (and I think I've tried various releases
from b17 to b20.1). So, I usually try to remember to use the "command prompt"
and the DIR command which works just fine. I also wave perl scripts over the
remote directories (scripts that do file globbing and file system traversals)
and they run fine...but they don't try to get all the file info that an 'ls
-l' would - ought to try out an 'ls' command from the Perl Power Tools set
sometime...

At any rate...since 'ls' is hardwired into my fingers and I wander into these
directories often enough, using cygwin can be painful, so I haven't gotten
fully into playing with it yet.

> Have people run any benchmarks comparing Cygwin, Uwin, NuTcracker, Interix,
> anything else out there?

That would be useful info!

Scott.Blachowicz@seaslug.org

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-03-14 16:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-13 10:04 [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released Earnie Boyd
2000-03-13 11:21 ` Re[2]: " Paul Sokolovsky
2000-03-13 15:16   ` Larry Hall (RFK Partners, Inc)
2000-03-13 15:56     ` Chris Faylor
2000-03-13 16:23       ` Jeff Sturm
2000-03-13 18:08         ` Cygwin performance (was [ANN] PW32 the...) Geoffrey Noer
2000-03-14 16:29           ` Scott Blachowicz [this message]
2000-03-14 21:04             ` Chris Faylor
2000-03-15  0:05             ` Re[2]: " Egor Duda
2000-03-13 16:13     ` [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 released Jeff Sturm
2000-03-13 16:17       ` Chris Faylor
2000-03-13 15:01 ` Re[2]: [ANN] PW32 the (alternative) Posix-over-Win32 layer 0.3.0 r Michael Hirmke
2000-03-15 13:43 Cygwin performance (was [ANN] PW32 the...) Heribert Dahms
2000-03-15 14:01 ` Larry Hall (RFK Partners, Inc)
2000-03-16  9:32 ` Scott Blachowicz
2000-03-16 10:22   ` Chris Faylor
2000-03-16 10:26 Chris Nappi
2000-03-16 10:43 ` Larry Hall (RFK Partners, Inc)

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=19940315002847.279871F1B@sabami.seaslug.org \
    --to=scott@sabami.seaslug.org \
    --cc=cygwin@sourceware.cygnus.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).