From: Valerie Clement <valerie.clement@bull.net>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Test results for ext4
Date: Wed, 04 Jun 2008 17:34:17 +0200 [thread overview]
Message-ID: <4846B5F9.8050906@bull.net> (raw)
In-Reply-To: <4844B71F.3070906@redhat.com>
Eric Sandeen wrote:
> Eric Sandeen wrote:
>> Valerie Clement wrote:
>>> Hi all,
>>>
>>> Since a couple of weeks, I did batches of tests to have some performance
>>> numbers for the new ext4 features like uninit_groups, flex_bg or
>>> journal_checksum on a 5TB filesystem.
>>> I tried to test allmost all combinations of mkfs and mount options, but
>>> I put only a subset of them in the result tables, the most significant
>>> for me.
>>>
>>> I had started to do these tests on a kernel 2.6.26-rc1, but I'd got several
>>> hangs and crashes occuring randomly outside ext4, sometimes in the slab
>>> code or in the scsi driver eg., and which were not reproductible.
>>> Since 2.6.26-rc2, no crash or hang occur with ext4 on my system.
>>>
>>> The first results and the test description are available here:
>>> http://www.bullopensource.org/ext4/20080530/ffsb-write-2.6.26-rc2.html
>>> http://www.bullopensource.org/ext4/20080530/ffsb-readwrite-2.6.26-rc2.html
>>>
>> One other question on the tests; am I reading correctly that ext3 used
>> "data=writeback" but ext4 used the default data=ordered mode?
>
> I was interested in the results, especially since ext3 seemed to pretty
> well match ext4 for throughput, although the cpu utilization differed.
>
> I re-ran the same ffsb profiles on an 8G, 4-way opteron box, connected
> to a "Vendor: WINSYS Model: SF2372" 2T hardware raid array with 512MB
> cache, connected via fibrechannel.
>
> Reads go pretty fast:
>
> # dd if=/dev/sdc bs=16M count=512 iflag=direct of=/dev/null
> 8589934592 bytes (8.6 GB) copied, 23.2257 seconds, 370 MB/s
>
> I got some different numbers....
>
> This was with e2fsprogs-1.39 for ext3, e2fsprogs-1.40.10 for ext4, and
> xfsprogs-2.9.8 for xfs.
I was using xfsprogs-2.9.0, maybe too old version...
I'm updating them and I'll run my tests again.
>
> I used defaults except; data=writeback for ext[34] and the nobarrier
> option for xfs. ext3 was made with 128 byte inodes, ext4 with 256-byte
> (new default). XFS used stock mkfs. I formatted the entire block
> device /dev/sdc.
>
> For the large file write test:
>
> MB/s CPU %
> ext3 140 90.7
> ext4 182 50.2
> xfs 222 145.0
>
> And for the small random readwrite test:
>
> trans/s CPU %
> ext3 9830 12.2
> ext4 11996 18.1
> xfs 13863 23.5
>
> Not sure what the difference is ...
>
> If you have your tests scripted up I'd be interested to run all the
> variations on this hardware as well, as it seems to show more throughput
> differences...
I added a link to the scripts I used in the test description section in:
http://www.bullopensource.org/ext4/20080530/ffsb-write-2.6.26-rc2.html
http://www.bullopensource.org/ext4/20080530/ffsb-readwrite-2.6.26-rc2.html
Valérie
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-04 15:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 15:50 Test results for ext4 Valerie Clement
2008-05-30 16:01 ` Eric Sandeen
2008-05-30 16:21 ` Valerie Clement
2008-05-30 16:23 ` Eric Sandeen
2008-05-30 16:28 ` Eric Sandeen
2008-06-02 13:07 ` Valerie Clement
2008-05-30 17:48 ` Mingming
2008-06-02 13:29 ` Valerie Clement
2008-05-30 18:12 ` Jose R. Santos
2008-06-02 13:44 ` Valerie Clement
2008-06-02 14:44 ` Jose R. Santos
2008-05-30 20:58 ` Eric Sandeen
2008-06-02 14:51 ` Valerie Clement
2008-05-31 19:35 ` Eric Sandeen
2008-06-02 13:20 ` Valerie Clement
2008-06-03 3:14 ` Eric Sandeen
2008-06-04 15:34 ` Valerie Clement [this message]
2008-06-04 15:41 ` Eric Sandeen
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=4846B5F9.8050906@bull.net \
--to=valerie.clement@bull.net \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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.