From: Curt Wohlgemuth <curtw@google.com>
To: Andreas Dilger <adilger@sun.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 without a journal: some benchmark results
Date: Thu, 8 Jan 2009 09:20:53 -0800 [thread overview]
Message-ID: <6601abe90901080920h2d2f4215tf8b886cefbb6e4b7@mail.gmail.com> (raw)
In-Reply-To: <20090108130357.GW13721@webber.adilger.int>
Hi Andreas:
On Thu, Jan 8, 2009 at 5:03 AM, Andreas Dilger <adilger@sun.com> wrote:
> On Jan 07, 2009 11:29 -0800, Curt Wohlgemuth wrote:
>> Iozone was run with the following command line:
>>
>> iozone -t (# threads) -s 2g -r 256k -I -T -i0 -i1 -i2
>>
>> I.e., throughput mode; 2GiB file; 256KiB buffer; O_DIRECT. Tests were
>> limited to
>
> How much RAM is on the test system? If the file size is only 2GB then
> it will likely fit into RAM, which is possibly why the performance
> numbers of all the filesystems is so close together. The other possibility
> is that a single disk is the performance bottleneck and all of the
> filesystems can feed a single disk at a reasonable rate.
Indeed, the system was not memory-limited at all. I've done some
playing around with how limiting memory affects random reads in iozone
with O_DIRECT, and have found that, as expected, ext4 is much less
affected than ext2. I'm assuming this is because the metadata isn't
in the page cache, and the far larger number of metadata blocks on
ext2 than ext4 in this case causes a bigger hit on ext2.
If I generate numbers on a low-memory system, I'll post them here too.
Thanks,
Curt
prev parent reply other threads:[~2009-01-08 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 19:29 Ext4 without a journal: some benchmark results Curt Wohlgemuth
2009-01-07 20:47 ` Theodore Tso
2009-01-07 21:19 ` Curt Wohlgemuth
2009-01-08 2:17 ` Theodore Tso
2009-01-08 13:03 ` Andreas Dilger
2009-01-08 17:20 ` Curt Wohlgemuth [this message]
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=6601abe90901080920h2d2f4215tf8b886cefbb6e4b7@mail.gmail.com \
--to=curtw@google.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
/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