linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Valerie Clement <valerie.clement@bull.net>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Performance degradation with FFSB between 2.6.20 and 2.6.21-rc7
Date: Wed, 18 Apr 2007 13:57:09 -0700	[thread overview]
Message-ID: <20070418135709.b499e050.akpm@linux-foundation.org> (raw)
In-Reply-To: <462622F8.10107@bull.net>

> On Wed, 18 Apr 2007 15:54:00 +0200 Valerie Clement <valerie.clement@bull.net> 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?
> 

That's a new discovery, thanks.

It could be due to I/O scheduler changes.  Which one are you using?  CFQ?

Or it could be that there has been some changed behaviour at the VFS/pagecache
layer: the VFS might be submitting little hunks of lots of files, rather than
large hunks of few files.

Or it could be a block-layer thing: perhaps some driver change has caused
us to be placing less data into the queue.  Which device driver is that machine
using?

Being a simple soul, the first thing I'll try when I get near a test box
will be

for i in $(seq 1 16)
do
	time dd if=/dev/zero of=$i bs=1M count=1024 &
done

  reply	other threads:[~2007-04-18 20:57 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 [this message]
2007-04-19  9:11   ` Valerie Clement
2007-04-19  9:03 ` Jens Axboe
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=20070418135709.b499e050.akpm@linux-foundation.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).