kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #29647
[Bug 1242812] Re: ext4 random block I/O write performance regression with 3.11 Saucy Kernel
I've installed the -proposed kernel and ran 10 iterations of a block
write soak test using stress-ng and measured the duration to perform
200000 I/O operations:
3.11.0-13-generic #20-Ubuntu : 127.6 seconds
3.11.0-14-generic #21-Ubuntu (-proposed): 78.5 seconds
so the proposed kernel does radically improve block I/O write
performance as expected.
I have also thrashed ext4 with multiple kernel builds for a few hours
and ext4 performs without any observable faults. I deem this verified
and passed.
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1242812
Title:
ext4 random block I/O write performance regression with 3.11 Saucy
Kernel
Status in “linux” package in Ubuntu:
Fix Committed
Bug description:
Commit e7ea81db5(ext4: restructure writeback path) introduced a
performance regression with random writes. Using tools such as
bonnie++, writes with dd or even stress testing with tools such as
'stress' one can observe a 10%-20% performance regression.
SRU Justification:
Commit e7ea81db5(ext4: restructure writeback path) introduced a
performance regression with random writes. Using tools such as
bonnie++, writes with dd or even stress testing with tools such as
'stress' one can observe a 10%-20% performance regression.
Impact:
Write performance is diminished causing a noticeable regression
compared to previous released kernels.
Fix:
Two patches are required:
a) upstream fix 9c12a83 which fixes the overly aggressive writing back of pages which ultimulately resulted in more seeking and
less performance.
b) commit aeac589a7 from the dev branch of kernel/git/tytso/ext4.git
which ensures no more pages than nr_to_write can be added to the
extent for mapping.
Testcase:
Using stress-ng on a 2 CPU machine run:
stress-ng --hdd 2 --hdd-ops 200000
(see: git://kernel.ubuntu.com/cking/stress-ng.git)
With the fix, this consistently runs ~10-20% faster than the non-fixed
kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242812/+subscriptions
References