From: alex chen <alex.chen@huawei.com>
To: <tytso@mit.edu>, Jan Kara <jack@suse.cz>, <linux-ext4@vger.kernel.org>
Cc: Joseph Qi <joseph.qi@huawei.com>
Subject: A doubt on journal_async_commit option
Date: Fri, 12 Dec 2014 14:03:32 +0800 [thread overview]
Message-ID: <548A8534.1050606@huawei.com> (raw)
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
Superblock info(-o journal_async_commit):
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent flex_bg sparse_super large_file
huge_file
uninit_bg dir_nlink extra_isize
Block size: 4096
Journal backup: inode blocks
Journal features: journal_checksum journal_async_commit
Journal size: 128M
Journal length: 32768
Journal sequence: 0x000017a6
Journal start: 1
Am I missing something?
---Alex
next reply other threads:[~2014-12-12 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 6:03 alex chen [this message]
2014-12-12 14:54 ` A doubt on journal_async_commit option Theodore Ts'o
2014-12-15 3:47 ` alex chen
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=548A8534.1050606@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).