All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: timotheus <timotheus@tstotts.net>
Cc: linux-xfs@oss.sgi.com
Subject: Re: tuning XFS for tiny files
Date: 19 Jul 2007 15:38:43 +0200	[thread overview]
Message-ID: <p73wswwwm1o.fsf@bingen.suse.de> (raw)
In-Reply-To: <m23azlbpl1.fsf@tstotts.net>

timotheus <timotheus@tstotts.net> writes:

> Hi. Is there a way to tune XFS filesystem parameters to better address
> the usage pattern of 10000s of tiny files in directories such as:
>     maildir directory
>     mh mail directory
>     ccache directory
> 
> My understanding is that XFS will always be much slower than reiserfs
> with respect to deleting 10000s files; but that XFS might be possible to
> tune toward more rapid read access of 10000s of tiny files.

-d agcount=1 at mkfs time might help (unless you have a lot of CPUs) 

-Andi

  parent reply	other threads:[~2007-07-19 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 17:15 tuning XFS for tiny files timotheus
2007-07-18 20:52 ` Eric Sandeen
2007-07-19 23:05   ` Nathan Scott
2007-07-19 13:38 ` Andi Kleen [this message]
2007-07-19 13:14   ` David Chinner
2007-07-19 13:54     ` Andi Kleen

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=p73wswwwm1o.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=timotheus@tstotts.net \
    /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.