From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 71641] Unreasonable performance degradation in ext4 with full data journaling
Date: Fri, 21 Mar 2014 08:48:34 +0000 [thread overview]
Message-ID: <bug-71641-13602-WpDXOgp3Ot@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71641-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=71641
Chia-Hung Chang <fredchang.tc@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Kernel Version|3.4.6 |3.11
--- Comment #5 from Chia-Hung Chang <fredchang.tc@gmail.com> ---
(In reply to Theodore Tso from comment #4)
> Could you retry your measurements using the latest kernel? At least 3.11,
> and preferably 3.13.
>
> We significantly optimized the write path for the nodelalloc case in 3.11.
> That should fix the average size being so small for the nodelalloc case:
>
>
Thanks for your advice. The kernel version is changed from 3.4 to 3.11. The
write throughput of data=journal is still only 40% of data=order. Do you think
what may be wrong in this mode ?
---------------------
Test environment--
CPU: Intel(R) Xeon(R) CPU E3-1225 v3 @ 3.20GHz
RAM:8GB
Filesystem:Ext4
Linux version: ubuntu-saucy with kernel 3.11
128MB ramdisk is used as journaling area
RAID0 are composed of 6 x 1TB HD
Command: time dd if=/dev/zero of= Write_File bs=1M count=5120
data=journal -> 398MB/s
data=ordered ->1.1GB/s
data=ordered ,nodelalloc -> 1G/s
blktrace results can be downloaded in
https://dl.dropboxusercontent.com/u/32959539/blktrace_with_3_11.7z
btt results can be downloaded in
https://dl.dropboxusercontent.com/u/32959539/BTT_with_3_11.7z
For linux 3.4, the write throughputs are
data=journal -> 397MB/s
data=ordered -> 937MB/s
data=ordered ,nodelalloc -> 863MB/s*
*PS. the previous data is mistaken, please use this version.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-03-21 8:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 11:39 [Bug 71641] New: Unreasonable performance degradation in ext4 with full data journaling bugzilla-daemon
2014-03-07 16:20 ` Theodore Ts'o
2014-03-07 16:20 ` [Bug 71641] " bugzilla-daemon
2014-03-07 17:57 ` bugzilla-daemon
2014-03-19 9:35 ` bugzilla-daemon
2014-03-20 4:09 ` bugzilla-daemon
2014-03-20 12:47 ` bugzilla-daemon
2014-03-21 8:16 ` bugzilla-daemon
2014-03-21 8:17 ` bugzilla-daemon
2014-03-21 8:44 ` bugzilla-daemon
2014-03-21 8:48 ` bugzilla-daemon [this message]
2014-03-21 16:04 ` bugzilla-daemon
2014-03-26 10:30 ` bugzilla-daemon
2014-03-26 13:40 ` bugzilla-daemon
2014-03-28 10:23 ` bugzilla-daemon
2014-03-28 10:55 ` bugzilla-daemon
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=bug-71641-13602-WpDXOgp3Ot@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).