From: raz ben yehuda <raziebe@gmail.com>
To: hch@lst.de
Cc: linux-kernel@vger.kernel.org, felixb@sgi.com, dgc@sgi.com
Subject: Huge XFS regression in 2.6.32 upto 2.6.38
Date: Tue, 12 Apr 2011 10:52:28 +0300 [thread overview]
Message-ID: <1302594748.2750.11.camel@raz.scalemp.com> (raw)
Christoph Hello
I am testing 2.6.38 with AIM benchmark.
I compared 2.6.38 to 2.6.27 and I noticed that 2.6.27 is much better than 2.6.38 when
doing sync random writes test over an xfs regular file over native Linux partition on top common sata disk.
I git bisected the problem and I reached this SHA1:
commit 13e6d5cdde0e785aa943810f08b801cadd0935df
Author: Christoph Hellwig <hch@lst.de>
Date: Mon Aug 31 21:00:31 2009 -0300
xfs: merge fsync and O_SYNC handling
The guarantees for O_SYNC are exactly the same as the ones we need to
make for an fsync call (and given that Linux O_SYNC is O_DSYNC the
equivalent is fdadatasync, but we treat both the same in XFS), except
with a range data writeout. Jan Kara has started unifying these two
path for filesystems using the generic helpers, and I've started to
look at XFS.
...
The bellow two tests presents the how different performance is before and patch:
#test 16) bisect 11
------------------------------------------------------------------------------------------------------------
Test Test Elapsed Iteration Iteration Operation
Number Name Time (sec) Count Rate (loops/sec) Rate (ops/sec)
------------------------------------------------------------------------------------------------------------
1 sync_disk_rw 30.71 19 0.61869 1583.85 Sync Random Disk Writes (K)/second
------------------------------------------------------------------------------------------------------------
#test 17 ) bisect 12
------------------------------------------------------------------------------------------------------------
1 sync_disk_rw 69.05 1 0.01448 37.07 Sync Random Disk Writes (K)/second
------------------------------------------------------------------------------------------------------------
Regards
Raz Ben-Yehuda
next reply other threads:[~2011-04-12 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 7:52 raz ben yehuda [this message]
2011-04-12 16:06 ` Christoph Hellwig
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=1302594748.2750.11.camel@raz.scalemp.com \
--to=raziebe@gmail.com \
--cc=dgc@sgi.com \
--cc=felixb@sgi.com \
--cc=hch@lst.de \
--cc=linux-kernel@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
Powered by JetHome