From: Kazuya Mio <k-mio@sx.jp.nec.com>
To: Yongqiang Yang <xiaoqiangnk@gmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
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: Mon, 06 Feb 2012 13:13:17 +0900 [thread overview]
Message-ID: <4F2F535D.7050202@sx.jp.nec.com> (raw)
In-Reply-To: <CAGBYx2ZATt7KG0oUvYSVWkwpVdio7iAJHHVHXFFkPqFp13Xi-Q@mail.gmail.com>
2012/02/03 22:28, Yongqiang Yang wrote:
> On Fri, Feb 3, 2012 at 3:49 PM, Kazuya Mio<k-mio@sx.jp.nec.com> wrote:
>> 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.
> And according to the data, maybe ext4+extent is also slower than ext4+noextent.
>
> What's the size of the fs? and what kind of the tested device?
I tested on Express5800/A1080a-S (4-way server with 8-core processors).
Filesystem size was 100GB. I used the 266GB LUN from the FC-SAN storage.
Regards,
Kazuya Mio
prev parent reply other threads:[~2012-02-06 4:16 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
2012-02-03 13:28 ` Yongqiang Yang
2012-02-06 4:13 ` Kazuya Mio [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=4F2F535D.7050202@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 \
--cc=xiaoqiangnk@gmail.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;
as well as URLs for NNTP newsgroup(s).