From: "Jeff Breidenbach" <jeff@jab.org>
To: Hannes Dorbath <light@theendofthetunnel.de>
Cc: xfs@oss.sgi.com
Subject: Re: tuning, many small files, small blocksize
Date: Sat, 16 Feb 2008 02:24:14 -0800 [thread overview]
Message-ID: <e03b90ae0802160224v600bd94exb2a1007ca7af7b65@mail.gmail.com> (raw)
In-Reply-To: <47B6ACC5.3030605@theendofthetunnel.de>
> That's maybe a bit paranoid, but on the other hand it should give good
> parallelism.
Yes, the goal is fast read performance for small files.
> mkfs.xfs -n size=16k -i attr=2 -l lazy-count=1,version=2,size=32m -b
> size=512 /dev/sda
>
> mount -onoatime,logbufs=8,logbsize=256k /dev/sda /mnt/xfs
This is highly appreciated, thank you very much.
> Requires kernel 2.6.23 and xfsprogs 2.9.5. As said, you might want to
> use an external log device.
I'm running vendor a supplied kernel of 2.6.22 and a quick test shows
the unsupported feature is lazy-count. How big a deal is it? Upgrading
the kernel before April is painful but I'll do it if important. Presumably
there's no simple way to migrate a non-lazy xfs filesytem to a lazy one.
PS. I don't know if this affects any parameters, but the biggest directory
will have approximately 1.5 million files. There are a few in the one to two
hundred thousand range, and then very many in the tens of thousands.
next prev parent reply other threads:[~2008-02-16 10:23 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 [this message]
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
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=e03b90ae0802160224v600bd94exb2a1007ca7af7b65@mail.gmail.com \
--to=jeff@jab.org \
--cc=light@theendofthetunnel.de \
--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