From: David Chinner <dgc@sgi.com>
To: Christian Kujau <christian@nerdbynature.de>
Cc: Iustin Pop <iusty@k1024.org>, xfs@oss.sgi.com, jasmin@pacifica.ch
Subject: Re: mkfs.xfs questions
Date: Wed, 6 Dec 2006 08:26:49 +1100 [thread overview]
Message-ID: <20061205212649.GV44411608@melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612051741520.22257@sheep.housecafe.de>
On Tue, Dec 05, 2006 at 05:46:15PM +0000, Christian Kujau wrote:
> On Sat, 2 Dec 2006, Iustin Pop wrote:
> >Hmm, I am pretty sure that it makes a difference, but only from personal
> >experience, not from benchmarks. A while ago, mkfs.xfs used to make <8M
> >logs even for big filesystems[0]. Nowadays it chooses a more sane value.
>
> I could not stand my own curiosity, so here it is:
> http://nerdbynature.de/wp/?cat=4
One line summary:
"The results however are a bit boring and I for one have no reason to tweak
these options for a desktop machine."
For that data set size you tested. However you might find a
difference if your tests actually write the data back to disk
because a lot of the tests are running out of cache.
> I think I'll repeat the benchmarks with bigger test sizes. The
> testscript can easily be adjusted to test more options/values.
I think you need to to have any hope of demonstrating a
difference in performance from the mkfs/mount options.
Typically, you need to be writing/reading files at least 2x the
size of memory and create/delete a fileset of at least 1,000,000
files to really determine differences in performance from
these parameters...
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2006-12-05 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 16:45 mkfs.xfs questions Jasmin Buchert
2006-12-01 4:23 ` Christian Kujau
2006-12-01 18:30 ` Iustin Pop
2006-12-01 23:59 ` Christian Kujau
2006-12-02 11:15 ` Iustin Pop
2006-12-05 17:46 ` Christian Kujau
2006-12-05 18:44 ` Iustin Pop
2006-12-05 21:26 ` David Chinner [this message]
2006-12-05 22:28 ` Christian Kujau
2006-12-06 15:57 ` Christian Kujau
2006-12-07 1:23 ` David Chinner
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=20061205212649.GV44411608@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=christian@nerdbynature.de \
--cc=iusty@k1024.org \
--cc=jasmin@pacifica.ch \
--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