From: Kazuya Mio <k-mio@sx.jp.nec.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: ext4 <linux-ext4@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 0/2] ext3: Reduce calling ext3_mark_inode_dirty() for speedup
Date: Fri, 03 Feb 2012 16:49:49 +0900 [thread overview]
Message-ID: <4F2B919D.1030307@sx.jp.nec.com> (raw)
In-Reply-To: <E2F2E1D0-8937-419F-8201-B2E9F3961AD7@dilger.ca>
2012/02/03 7:36, Andreas Dilger wrote:
>> filesystem time(sec) call extX_mark_inode_dirty(times)
>> ---
>> ext3 220.5 50,338,104
>> ext3 (patched) 196.3 25,169,658
>> ext4 (*1) 190.3 28,465,799
>> ext4 (*2) 201.5 27,963,473
>> ext4 (default) 223.3 14,026,118
>>
>> *1 disable ext4-specific options (delalloc, extent, and so on)
>> *2 disable only delalloc option
> This shows that ext4 with extents+delalloc is _slower_ than ext3, which
> is very strange. In other similar tests of write performance (see
One more thing is that ext4+delalloc is slower than ext4+nodelalloc.
> http://downloads.linux.hp.com/~enw/ext4/3.2/large_file_creates.html,
> showing multi-threaded 1GB file writes) ext4 is much faster than ext3.
I guess write buffer size of my test is different from ffsb's one.
My test calls write systemcall every time one block is allocated,
so it is close to the stress test I think.
> Looking at your original email, is ext4 being tested on a RHEL 5.5
> (2.6.18) kernel, or a more recent kernel? It would be more useful
> to run this on a more modern kernel, since the ext4 code backported
> to RHEL5 was barely supporting delalloc at all, if I remember correctly.
I tested on the recent kernel (3.3-rc1).
I also tested on RHEL5.5, and its result showed that ext3 was much slower than
the recent kernel's one.
filesystem time(sec)
---
ext3(RHEL5.5) 438.6
ext3(3.3-rc1) 220.5
Regards,
Kazuya Mio
next prev parent reply other threads:[~2012-02-03 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 8:41 [PATCH 0/2] ext3: Reduce calling ext3_mark_inode_dirty() for speedup Kazuya Mio
2012-01-30 20:36 ` Andreas Dilger
2012-01-31 5:03 ` Kazuya Mio
2012-02-01 8:35 ` Kazuya Mio
2012-02-02 22:36 ` Andreas Dilger
2012-02-03 7:49 ` Kazuya Mio [this message]
2012-02-03 13:28 ` Yongqiang Yang
2012-02-06 4:13 ` Kazuya Mio
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=4F2B919D.1030307@sx.jp.nec.com \
--to=k-mio@sx.jp.nec.com \
--cc=adilger@dilger.ca \
--cc=jack@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).