From: "William M. (Mike) Miller" <william.m.miller@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Performance of "ls -F"
Date: Thu, 21 Jan 2016 18:34:00 -0000 [thread overview]
Message-ID: <CAH5rLZVWiGz2n-3Ru-C0_5KU-Cc4NipJPn1NQVphN2UetUK4iA@mail.gmail.com> (raw)
In-Reply-To: <loom.20160121T163405-489@post.gmane.org>
On Thu, Jan 21, 2016 at 10:44 AM, Achim Gratz <Stromeko@nexgo.de> wrote:
> I am finding a large performance gap between plain "ls" and "ls -F" in a
> directory with many files on a network share (NetApp disguised as NTFS if
> that matters). This has been there for quite a while, I've just now
> realized what the reason was (I have "ls -F" as an alias for "ls" in my
> interactive shells). In a directory with 1300 files, a plain "ls" completes
> in 0.3s, while "ls -F" requires about 95s. Determining the file class seems
> to require around 70...90ms per file, which I can confirm also for
> directories with a lot less files. What's involved in that determination
> that takes such a long time?
The overhead appears to be in checking for executable files; using
--file-type instead of -F, which just omits the '*' category, reduces
the time for ls in one of my (local) large directories from over one
second to 0.04 seconds.
--
William M. (Mike) Miller | Edison Design Group
william.m.miller@gmail.com
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-01-21 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 18:10 Achim Gratz
2016-01-21 18:34 ` William M. (Mike) Miller [this message]
2016-01-21 19:09 ` Achim Gratz
2016-01-21 19:56 ` Bill Smith
2016-01-22 15:09 ` Achim Gratz
2016-01-22 22:19 ` Corinna Vinschen
2016-01-22 23:21 ` Achim Gratz
2016-01-23 19:55 ` Corinna Vinschen
2016-01-25 20:54 ` Achim Gratz
2016-01-25 21:03 ` Corinna Vinschen
2016-01-21 19:54 ` Bill Smith
2016-01-21 21:40 ` Achim Gratz
2016-01-25 20:08 Lemke, Michael ST/HZA-ZIC2
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=CAH5rLZVWiGz2n-3Ru-C0_5KU-Cc4NipJPn1NQVphN2UetUK4iA@mail.gmail.com \
--to=william.m.miller@gmail.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).