From: Vladimir Saveliev <vs@namesys.com>
To: Ron Peterson <rpeterso@mtholyoke.edu>
Cc: 7eggert@gmx.de,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: slow directory listing
Date: Wed, 15 Jun 2005 15:05:22 +0400 [thread overview]
Message-ID: <1118833522.3603.148.camel@tribesman.namesys.com> (raw)
In-Reply-To: <20050613120520.GA26921@mtholyoke.edu>
Hello
On Mon, 2005-06-13 at 16:05, Ron Peterson wrote:
> On Sat, Jun 11, 2005 at 12:12:52AM +0200, Bodo Eggert wrote:
> > Ron Peterson <rpeterso@mtholyoke.edu> wrote:
> > > On Fri, Jun 10, 2005 at 10:37:20AM -0400, rpeterso wrote:
> >
> > >> I'm setting up a new mail server, and am testing/tweaking IO. I have
> > >> two directories: /test/a which contains 750 mbox files totalling 8GB,
> > >> and /test/a2, which contains the exact same number of files, same names,
> > >> all zero length.
> > >> ...
> > >> The times taken to do a directory listing are significantly different.
> > >
Which filesystem is used for /test?
> > > I've become more confused, if that's possible. I was just editing some
> > > test script in emacs. As part of the script creation process I used the
> > > M-! command to pipe the output of 'ls /test/a' into a buffer. It
> > > snapped back almost instantly.
> >
> > Try ls|cat and take a look at $LS_OPTIONS and $LS_COLORS. I suspect your
> > ls tries to use some magic on the files to determine the color.
>
> ls was aliased to 'ls -F', it just took me a while to notice...
next prev parent reply other threads:[~2005-06-15 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4dSQ6-1vz-27@gated-at.bofh.it>
[not found] ` <4dTCx-2d8-21@gated-at.bofh.it>
2005-06-10 22:12 ` slow directory listing Bodo Eggert
2005-06-13 12:05 ` Ron Peterson
2005-06-15 11:05 ` Vladimir Saveliev [this message]
2005-06-10 14:37 Ron Peterson
2005-06-10 15:21 ` Ron Peterson
2005-06-13 6:41 ` David Weinehall
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=1118833522.3603.148.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@mtholyoke.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.