From: Eric Sandeen <sandeen@sandeen.net>
To: prad <prad@towardsfreedom.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: altering defaults
Date: Sun, 05 Jun 2011 22:47:44 -0500 [thread overview]
Message-ID: <4DEC4DE0.5090503@sandeen.net> (raw)
In-Reply-To: <8762onaq19.fsf@psinom.home>
On 6/3/11 10:33 AM, prad wrote:
> i'm new to xfs (courtesy of most helpful and encouraging commentary by
> stan hoeppner!) and i've seen some advice which says to make the
> block size -> 512
> directory size -> 4096
>
> on the other hand, i've also come across webpages which say don't mess
> around! keep the defaults as they are unless you are absolutely sure
> that changing it suits your purpose and know why.
Yup. See "Q: I want to tune my XFS filesystems for <something> "
http://xfs.org/index.php/XFS_FAQ#Q:_I_want_to_tune_my_XFS_filesystems_for_.3Csomething.3E
> my question is for the data storage area on a web/email server. we're
> mainly going to have small files there and the email part will have only
> temporary files for the most part since people will download (ie pop).
>
> it makes sense to make the block size = 512, but i wonder if it really
> matters noticeably. the server is not a heavily visited one and only on
> very rare occasions will we get around 50000 hits/day - most of the time
> we're looking at under 10000 and that is with all the domains combined.
If space efficiency is a consideration then smaller blocksizes might
be useful. Not so much for hits per day, but for how many files you expect
to store at any one time; you'll waste ((blocksize / 2) * nr files) on average.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-06 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 15:33 altering defaults prad
2011-06-05 16:23 ` Michael Weissenbacher
2011-06-06 3:47 ` Eric Sandeen [this message]
2011-06-06 16:26 ` prad
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=4DEC4DE0.5090503@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@oss.sgi.com \
--cc=prad@towardsfreedom.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