10.06.2010 04:47, Dave Chinner wrote:
On Wed, Jun 09, 2010 at 11:11:53PM +0400, Michael Tokarev wrote:
09.06.2010 11:47, Dave Chinner wrote:
On Wed, Jun 09, 2010 at 10:43:37AM +0400, Michael Tokarev wrote:
09.06.2010 03:18, Dave Chinner wrote:
On Wed, Jun 09, 2010 at 12:34:00AM +0400, Michael Tokarev wrote:
Simple test doing random reads or writes of 4k blocks in a 1Gb
file located on an xfs filesystem, Mb/sec:
read write write
2.6.27 xfs 1.17 3.69 3.80
2.6.32 xfs 1.26 0.52 5.10
2.6.32 ext3 1.19 4.91 5.02
Out of curiousity, what does 2.6.34 get on this workload?
2.6.34 works quite well:
2.6.34 xfs 1.14 4.75 5.00
Ok, so we are looking at a fixed regression, then. What stable
version of 2.6.32 are you testing? A large number of XFS fixes went
into 220.127.116.11 (IIRC, it might have been .13), so maybe the problem
is fixed there. Alternatively, can you use 2.6.34 rather than
2.6.32, or bisect the regression down to a specific set of fixes so
we can consider whether a backport is worth the effort?
I tried 18.104.22.168. A few previous versions too, but all recent
testing were with 22.214.171.124. So no, the fix is not in 2.6.32.y
yet, since .15 is the latest currently.
Too bad it'd be very difficult for me to do any bisection, -- users
are not comfortable at all already due to all my experiments, --
f.e. their reports that are collecting for whole night stopped
working completely since a few days ago (because every night I'm
rebooting the machine).
Yes it'd be nice to have this fixed in 2.6.32.y. And I promise I'll
try to find time for bisection (but not promise the tries will be
successful... ;). Definitely worth a try anyway.