public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valerie Clement <valerie.clement@bull.net>
To: Andrew Morton <akpm@linux-foundation.org>
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: Thu, 19 Apr 2007 11:11:45 +0200	[thread overview]
Message-ID: <46273251.4000403@bull.net> (raw)
In-Reply-To: <20070418135709.b499e050.akpm@linux-foundation.org>

Andrew Morton wrote:
> 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
> 

I tried first the test with dd, the results are similar to those of FFSB 
tests, about 15 percent of degradation between 2.6.20.7 and 2.6.21-rc7.

I'm using the CFQ I/O scheduler. I changed it to the "deadline" one and 
I don't have any more the problem, I've got similar throughput values 
with 2.6.20.7 and 2.6.21-rc7 kernels.
So can we conclude that it's due to the CFQ scheduler?

I also checked the device driver used, the revision number is the same 
in 2.6.20 and 2.6.21.

   Valérie


  reply	other threads:[~2007-04-19  9:12 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 [this message]
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=46273251.4000403@bull.net \
    --to=valerie.clement@bull.net \
    --cc=akpm@linux-foundation.org \
    --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