* A doubt on journal_async_commit option
@ 2014-12-12 6:03 alex chen
2014-12-12 14:54 ` Theodore Ts'o
0 siblings, 1 reply; 3+ messages in thread
From: alex chen @ 2014-12-12 6:03 UTC (permalink / raw)
To: tytso, Jan Kara, linux-ext4; +Cc: Joseph Qi
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: A doubt on journal_async_commit option
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
0 siblings, 1 reply; 3+ messages in thread
From: Theodore Ts'o @ 2014-12-12 14:54 UTC (permalink / raw)
To: alex chen; +Cc: Jan Kara, linux-ext4, Joseph Qi
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: A doubt on journal_async_commit option
2014-12-12 14:54 ` Theodore Ts'o
@ 2014-12-15 3:47 ` alex chen
0 siblings, 0 replies; 3+ messages in thread
From: alex chen @ 2014-12-15 3:47 UTC (permalink / raw)
To: Theodore Ts'o; +Cc: Jan Kara, linux-ext4, Joseph Qi
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
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-12-15 3:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).