From: alex chen <alex.chen@huawei.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, <linux-ext4@vger.kernel.org>,
Joseph Qi <joseph.qi@huawei.com>
Subject: Re: A doubt on journal_async_commit option
Date: Mon, 15 Dec 2014 11:47:46 +0800 [thread overview]
Message-ID: <548E59E2.3080001@huawei.com> (raw)
In-Reply-To: <20141212145443.GB17783@thunk.org>
On 2014/12/12 22:54, Theodore Ts'o wrote:
> On Fri, Dec 12, 2014 at 02:03:32PM +0800, alex chen wrote:
>> This commit 0e3d2a6313(ext4: Fix async commit mode to be safe by using
>> a barrier) show that using journal_async_commit feature has a 50%
>> performance improvement. But I tested in SUSE Linux Enterprise Server
>> 11 SP3(linux kernel 3.0.93) and Red Hat Enterprise linux 6.4(linux
>> kernel 2.6.32), the result show this feature has no performance
>> improvement.
>> My test command:
>> mount /dev/sdb /mnt/sdb
>> ./fs_mark -d /mnt/sdb/ -s 10240 -n 1000
>> umount
>>
>> mount /dev/sdb /mnt/sdb -o journal_async_commit
>> ./fs_mark -d /mnt/sdb/ -s 10240 -n 1000
>> umount
>>
>> My test result:
>> FSUse% Count Size Files/sec App Overhead
>> 6 1000 10240 42.1 10671
>> vs.
>> -o journal_async_commit
>> FSUse% Count Size Files/sec App Overhead
>> 6 1000 10240 63.9 10625
>
> Um, the files per second went up from 42.1 to 63.9 --- that's a 50%
> improvement, yes?
>
> - Ted
Yes, I understand it. Thank you!
> --
> 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
>
>
prev parent reply other threads:[~2014-12-15 3:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 6:03 A doubt on journal_async_commit option alex chen
2014-12-12 14:54 ` Theodore Ts'o
2014-12-15 3:47 ` alex chen [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=548E59E2.3080001@huawei.com \
--to=alex.chen@huawei.com \
--cc=jack@suse.cz \
--cc=joseph.qi@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).