From: David Chinner <dgc@sgi.com>
To: Jeff Breidenbach <jeff@jab.org>
Cc: xfs@oss.sgi.com
Subject: Re: tuning, many small files, small blocksize
Date: Tue, 19 Feb 2008 09:53:35 +1100 [thread overview]
Message-ID: <20080218225335.GR155407@sgi.com> (raw)
In-Reply-To: <e03b90ae0802152101t2bfa4644kcca5d6329239f9ff@mail.gmail.com>
On Fri, Feb 15, 2008 at 09:01:10PM -0800, Jeff Breidenbach wrote:
> I'm testing xfs for use in storing 100 million+ small files
> (roughly 4 to 10KB each) and some directories will contain
> tens of thousands of files. There will be a lot of random
> reading, and also some random writing, and very little
> deletion.
.....
> a) Should I just go with the 512 byte blocksize or is that going to be
> bad for some performance reason? Going to 1024 is no problem,
> but I'd prefer not to waste 20% of the partition capacity by using 4096.
I'd suggest wasting 20% of disk space and staying with 4k block size.
> b) Are there any other mkfs.xfs paramters that I should play with.
Large directory block size (-n size=XXX), esp. if you are putting
thousands of files per directory....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-02-18 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 5:01 tuning, many small files, small blocksize Jeff Breidenbach
2008-02-16 9:28 ` Hannes Dorbath
2008-02-16 10:24 ` Jeff Breidenbach
2008-02-16 20:30 ` Jeff Breidenbach
2008-02-19 0:48 ` Timothy Shimmin
2008-02-16 12:23 ` pg_xfs2
2008-02-18 22:53 ` David Chinner [this message]
2008-02-18 23:12 ` Linda Walsh
2008-02-18 23:51 ` David Chinner
2008-02-19 1:03 ` Linda Walsh
2008-02-19 2:49 ` David Chinner
2008-02-19 4:58 ` Jeff Breidenbach
2008-02-19 8:27 ` Peter Grandi
2008-02-19 11:44 ` Hannes Dorbath
2008-02-19 21:24 ` Peter Grandi
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=20080218225335.GR155407@sgi.com \
--to=dgc@sgi.com \
--cc=jeff@jab.org \
--cc=xfs@oss.sgi.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