From: Jens Axboe <jens.axboe@oracle.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Performance degradation with FFSB between 2.6.20 and 2.6.21-rc7
Date: Thu, 19 Apr 2007 11:03:47 +0200 [thread overview]
Message-ID: <20070419090346.GE20928@kernel.dk> (raw)
In-Reply-To: <462622F8.10107@bull.net>
On Wed, Apr 18 2007, Valerie Clement wrote:
>
> Running benchmark tests (FFSB) on an ext4 filesystem, I noticed a
> performance degradation (about 15-20 percent) in sequential write tests
> between 2.6.19-rc6 and 2.6.21-rc4 kernels.
>
> I ran the same tests on ext3 and XFS filesystems and I saw the same
> performance difference between the two kernel versions for these two
> filesystems.
>
> I have also reproduced it between 2.6.20.7 and 2.6.21-rc7.
> The FFSB tests run 16 threads, each creating 1GB files. The tests were
> done on the same x86_64 system, with the same kernel configuration and
> on the same scsi device. Below are the throughput values given by FFSB.
>
> kernel XFS ext3
> ----------
> 2.6.20.7 48 MB/sec 44 MB/sec
>
> 2.6.21-rc7 38 MB/sec 37 MB/sec
>
> Did anyone else run across the problem?
> Is there a known issue?
Please tell me how you are running ffsb, and also please include a
dmessg from a booted system.
--
Jens Axboe
next prev parent reply other threads:[~2007-04-19 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 13:54 Performance degradation with FFSB between 2.6.20 and 2.6.21-rc7 Valerie Clement
2007-04-18 20:57 ` Andrew Morton
2007-04-19 9:11 ` Valerie Clement
2007-04-19 9:03 ` Jens Axboe [this message]
2007-04-19 9:31 ` Valerie Clement
2007-04-19 11:58 ` Jens Axboe
2007-04-19 12:41 ` Jens Axboe
2007-04-19 12:45 ` Valerie Clement
2007-04-19 12:46 ` Jens Axboe
2007-04-19 13:22 ` Valerie Clement
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=20070419090346.GE20928@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valerie.clement@bull.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.