From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: LWN.net article: creating 1 billion files -> XFS looses
Date: Tue, 7 Sep 2010 00:58:40 +0200 [thread overview]
Message-ID: <201009070058.40849@zmi.at> (raw)
In-Reply-To: <20100906220410.GD7362@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 1231 bytes --]
On Dienstag, 7. September 2010 Dave Chinner wrote:
> # mkfs.xfs -d size=64k
>
> Will speed up large directory operations by at least an order of
> magnitude.
I've read the man page for mkfs.xfs, but I couldn't find out if using
mkfs -d su=64k,sw=2
would be a redundant (and superior) option for that? I'd guess so,
reading the description of sunit:
sunit=value
This is used to specify the stripe unit for a RAID device or a
logical volume. The value has to be specified in 512-byte block units.
Use the su suboption to specify the stripe unit size in bytes. This
suboption ensures that data allocations will be stripe unit aligned when
the current end of file is being extended and the file size is larger
than 512KiB. Also inode allocations and the internal log will
be stripe unit aligned.
Or would I still need to use size=64k?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-06 22:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 11:12 LWN.net article: creating 1 billion files -> XFS looses Michael Monnerie
2010-08-19 12:05 ` Christoph Hellwig
2010-08-19 12:45 ` Michael Monnerie
2010-08-19 13:55 ` Stan Hoeppner
2010-08-20 7:55 ` Dave Chinner
2010-08-19 13:10 ` Emmanuel Florac
2010-09-06 13:42 ` Emmanuel Florac
2010-09-06 22:04 ` Dave Chinner
2010-09-06 22:58 ` Michael Monnerie [this message]
2010-09-07 3:31 ` Dave Chinner
2010-09-07 6:20 ` Michael Monnerie
2010-09-07 7:01 ` Dave Chinner
2010-09-08 5:42 ` Michael Monnerie
2010-09-07 6:46 ` Emmanuel Florac
2010-09-16 10:13 ` LWN.net article: creating 1 billion files -> Tests we did Emmanuel Florac
2010-09-16 21:53 ` Stan Hoeppner
2010-09-17 7:54 ` Michael Monnerie
2010-09-17 19:29 ` Peter Grandi
2010-09-18 11:25 ` Emmanuel Florac
2010-09-18 11:16 ` Emmanuel Florac
2010-09-17 19:57 ` Peter Grandi
2010-09-18 11:39 ` Emmanuel Florac
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=201009070058.40849@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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 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.