From: "Ted Ts'o" <tytso@mit.edu>
To: Kay Diederichs <Kay.Diederichs@uni-konstanz.de>
Cc: linux <linux-kernel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Karsten Schaefer <karsten.schaefer@uni-konstanz.de>
Subject: Re: ext4 performance regression 2.6.27-stable versus 2.6.32 and later
Date: Thu, 29 Jul 2010 22:20:55 -0400 [thread overview]
Message-ID: <20100730022055.GL4506@thunk.org> (raw)
In-Reply-To: <4C508A54.7070002@uni-konstanz.de>
On Wed, Jul 28, 2010 at 09:51:48PM +0200, Kay Diederichs wrote:
>
> When looking at the I/O statistics while the benchmark is running, we
> see very choppy patterns for 2.6.32, but quite smooth stats for
> 2.6.27-stable.
Could you try to do two things for me? Using (preferably from a
recent e2fsprogs, such as 1.41.11 or 12) run filefrag -v on the files
created from your 2.6.27 run and your 2.6.32 run?
Secondly can capture blktrace results from 2.6.27 and 2.6.32? That
would be very helpful to understand what might be going on.
Either would be helpful; both would be greatly appreciated.
Thanks,
- Ted
next prev parent reply other threads:[~2010-07-30 2:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 19:51 ext4 performance regression 2.6.27-stable versus 2.6.32 and later Kay Diederichs
2010-07-28 21:00 ` Greg Freemyer
2010-08-02 10:47 ` Kay Diederichs
2010-08-02 16:04 ` Henrique de Moraes Holschuh
2010-08-02 16:10 ` Henrique de Moraes Holschuh
2010-07-29 23:28 ` Dave Chinner
2010-08-02 14:52 ` Kay Diederichs
2010-08-02 16:12 ` Eric Sandeen
2010-08-02 21:08 ` Kay Diederichs
2010-08-03 13:31 ` Kay Diederichs
2010-07-30 2:20 ` Ted Ts'o [this message]
2010-07-30 21:01 ` Kay Diederichs
2010-08-01 23:02 ` Ted Ts'o
2010-08-02 15:28 ` Kay Diederichs
[not found] ` <4C56E47B.8080600@uni-konstanz.de>
[not found] ` <20100802202123.GC25653@thunk.org>
2010-08-04 8:18 ` Kay Diederichs
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=20100730022055.GL4506@thunk.org \
--to=tytso@mit.edu \
--cc=Kay.Diederichs@uni-konstanz.de \
--cc=karsten.schaefer@uni-konstanz.de \
--cc=linux-ext4@vger.kernel.org \
--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