From: Hannes Dorbath <light@theendofthetunnel.de>
To: Jeff Breidenbach <jeff@jab.org>
Cc: xfs@oss.sgi.com
Subject: Re: tuning, many small files, small blocksize
Date: Sat, 16 Feb 2008 10:28:37 +0100 [thread overview]
Message-ID: <47B6ACC5.3030605@theendofthetunnel.de> (raw)
In-Reply-To: <e03b90ae0802152101t2bfa4644kcca5d6329239f9ff@mail.gmail.com>
Jeff Breidenbach wrote:
> The underlying disks use linux software RAID-1
> manged by mdadm with 5X redundancy. E.g. 5 drives that
> completely mirror each other.
That's maybe a bit paranoid, but on the other hand it should give good
parallelism.
> 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 don't think there is performance problem with 512 byte block size, but
it limits the internal log size to 32MB. You might want to use a larger
external log.
> b) Are there any other mkfs.xfs paramters that I should play with.
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
Requires kernel 2.6.23 and xfsprogs 2.9.5. As said, you might want to
use an external log device.
--
Best regards,
Hannes Dorbath
next prev parent reply other threads:[~2008-02-16 9:28 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 [this message]
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
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=47B6ACC5.3030605@theendofthetunnel.de \
--to=light@theendofthetunnel.de \
--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 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.