From: Eric Sandeen <sandeen@sandeen.net>
To: "Igor A. Valcov" <viaprog@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: XFS filesystem performance drop in kernels 2.6.16+
Date: Thu, 09 Nov 2006 11:44:20 -0600 [thread overview]
Message-ID: <455368F4.8080203@sandeen.net> (raw)
In-Reply-To: <bde600590611090930g3ab97aq3c76d7bca4ec267f@mail.gmail.com>
Igor A. Valcov wrote:
> Hello,
>
> For one of our projects we have a test program that measures file
> system performance by writing up to 1000 files simultaneously. After
> installing kernel v2.6.16 we noticed that XFS performance dropped by a
> factor of 5 (tests that took around 4 minutes on kernel 2.6.15 now
> take around 20 minutes to complete).
Ouch.
> We then checked all kernels
> starting from 2.6.16 up to 2.6.19-rc5 with the same unpleasant result.
> The funny thing about all this is that we chose XFS for that
> particular project specifically because it was about 5 times faster
> with the tests than the other file systems. Now they all take about
> the same time.
>
> I also noticed that I/O barriers were introduced in v2.6.16 and
> thought they may be the cause, but mounting the file system with
> 'nobarrier' doesn't seem to affect the performance in any way.
>
> Any thoughts on the matter are appreciated.
Can you provide the test?
-Eric
next prev parent reply other threads:[~2006-11-09 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 17:30 XFS filesystem performance drop in kernels 2.6.16+ Igor A. Valcov
2006-11-09 17:44 ` Eric Sandeen [this message]
2006-11-09 18:08 ` Russell Cattelan
2006-11-10 1:10 ` David Chinner
2006-11-10 3:36 ` Eric Sandeen
2006-11-10 11:59 ` Jan Engelhardt
2006-11-10 13:16 ` Igor A. Valcov
2006-11-10 14:44 ` Igor A. Valcov
2006-11-10 17:14 ` Eric Sandeen
2006-11-11 6:52 ` Andrew Morton
2006-11-11 10:55 ` Jan Engelhardt
2006-11-13 20:05 ` Tom Vier
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=455368F4.8080203@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-kernel@vger.kernel.org \
--cc=viaprog@gmail.com \
/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