All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Norbert Preining <preining@logic.at>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 slow on links
Date: Tue, 19 Jun 2012 22:15:00 -0500	[thread overview]
Message-ID: <4FE14034.6070800@redhat.com> (raw)
In-Reply-To: <20120620002014.GA25471@gamma.logic.tuwien.ac.at>

On 6/19/12 7:20 PM, Norbert Preining wrote:
> Dear all
> 
> (please Cc)
> 
> I recently had to track down a big delay in one of my Debian packages,
> and it turned out that it seems to be due to ext4 being *horribly*
> slow on dealing with symlinks.
> 
> On my system, if I create a directory with 8000 symlinks (that is
> a real case of a font package shipping special encoded files) and
> the symlink targets are "far away" (long names), then, after 
> a reboot a simply
> 	ls -l
> in this directory took 1m20sec. While on second run it is down to 2secs
> (nice caching).

As Ted said, the targets might be far-flung.  If you do /bin/ls -l instead
of maybe an aliased ls which stats everything to make pretty colors,
is that faster?

-Eric

      parent reply	other threads:[~2012-06-20  3:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20  0:20 Ext4 slow on links Norbert Preining
2012-06-20  2:19 ` Ted Ts'o
2012-06-20  3:38   ` Norbert Preining
2012-06-20  3:57     ` Eric Sandeen
2012-06-20  4:01       ` Norbert Preining
2012-06-20  5:18       ` Norbert Preining
2012-06-20 14:07         ` Eric Sandeen
2012-06-21  2:28           ` Norbert Preining
2012-06-21  4:05             ` Eric Sandeen
2012-06-21  4:50               ` Norbert Preining
2012-06-21  5:18                 ` Andreas Dilger
2012-06-21  6:55                   ` Norbert Preining
2012-06-22  9:53               ` Bernd Schubert
2012-06-22 14:08                 ` Ted Ts'o
2012-06-20 19:35       ` Eric Sandeen
2012-06-20  3:15 ` Eric Sandeen [this message]

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=4FE14034.6070800@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=preining@logic.at \
    /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.