From: "Jose R. Santos" <jrs@us.ibm.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Mingming Cao <cmm@us.ibm.com>
Subject: Re: Test results for ext4
Date: Fri, 30 May 2008 13:12:39 -0500 [thread overview]
Message-ID: <20080530131239.6d93f1d9@rx8> (raw)
In-Reply-To: <48402253.8040407@bull.net>
On Fri, 30 May 2008 17:50:43 +0200
Valerie Clement <valerie.clement@bull.net> 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
>
> I will complete them in the next days.
>
> In the first batch of tests, I compare the I/O throughput to create
> 1-GB files on disk in different configurations. The CPU usage is also
> given to show mainly how the delayed allocation feature reduces it.
> The average number of extents per file shows the impact of the
> multiblock allocator and the flex_bg grouping on the file
> fragmentation. At last, the fsck time shows how the uninit_groups
> feature reduces the e2fsck duration.
>
> In the second batch of tests, the results show improvements in
> transactions -per-second throughput when doing small files writes,
> reads and creates when using the flex_bg grouping.
> The same ffsb test on an XFS filesystem hangs, I will try to have
> traces.
>
> If you are interested in other tests, please let me know.
How about adding the following in "[filesystem0]" to age the filesystem:
agefs=1
[threadgroup0]
num_threads=10
write_size=40960
write_blocksize=4096
create_weight=10
append_weight=10
delete_weight=1
[end0]
desired_util=0.80
This will age the filesystem until it reaches 80% utilization before
starting the benchmark. Since a 5TB disk will take a while to age, I
suggest trying this on just a few runs.
>
> Valérie
>
-JRS
--
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-05-30 18:14 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 [this message]
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
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=20080530131239.6d93f1d9@rx8 \
--to=jrs@us.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=valerie.clement@bull.net \
/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