public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: David Chinner <dgc@sgi.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	timotheus <timotheus@tstotts.net>,
	linux-xfs@oss.sgi.com
Subject: Re: tuning XFS for tiny files
Date: Thu, 19 Jul 2007 15:54:59 +0200	[thread overview]
Message-ID: <20070719135459.GA16552@one.firstfloor.org> (raw)
In-Reply-To: <20070719131401.GW31489@sgi.com>

On Thu, Jul 19, 2007 at 11:14:01PM +1000, David Chinner wrote:
> On Thu, Jul 19, 2007 at 03:38:43PM +0200, Andi Kleen wrote:
> > 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) 
> 
> Yeah, might help, but it's not good for being able to repair the
> filesystem - repair will be unable to find a secondary superblock
> to compare the primary against and abort.....

Any reason why it aborts? It could just continue with a warning, couldn't it?

> -d agcount is only good for science experiments, not production
> systems ;)

XFS small file performance needs a lot of science.

-Andi

      reply	other threads:[~2007-07-19 14:18 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
2007-07-19 13:14   ` David Chinner
2007-07-19 13:54     ` Andi Kleen [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=20070719135459.GA16552@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=dgc@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox