mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Timothy Miller <miller@techsource.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Consistently slower 3ware RAID performance under 2.6.4
Date: Fri, 2 Apr 2004 15:47:18 -0800	[thread overview]
Message-ID: <20040402154718.43f16ea9.akpm@osdl.org> (raw)
In-Reply-To: <406D89B8.4090308@techsource.com>

Timothy Miller <miller@techsource.com> wrote:
>
> ## Performance with "2.4.25-gentoo":
> 
> The read test here takes 21.6 seconds which is about 47MB/sec.  This is 
> a correct number, because I have measured the maximum read throughput 
> from each drive to be 47MB/sec.
> 
> The write test here takes 2 minutes, 2.5 seconds.  This translates to 
> 8.35MB/sec.  This is what I'm working with 3ware to correct, but let's 
> call this the baseline write performance.
> 
> 
> ## Performance with "2.6.4-gentoo-r1":
> 
> The read test here takes 33.9 seconds.  That's down to about 30MB/sec.
> 
> The write test here takes 2 minutes, 44.2 seconds.  That is down to 
> 6.2MB/sec.
> 

You cannot compare 2.4 and 2.6 kernel write performance with `dd', because
the kernels are tuned differently.  2.6 kernels are tuned to leave less
dirty pages in memory than a 2.4 kernel.  Hence when your dd has finished,
40% of memory will be dirty (needing writeout) under 2.6, but this figure
is 60% on 2.4.

So the 2.6 kernel does more writeout during the dd run and less writeout
after dd has finished.  The 2.4 kernel does less writeout during the dd run
and more writeout after dd has finished.

To compare IO performance you'll need to set 2.6's /proc/sys/vm/dirty_ratio
to 60 and /proc/sys/vm/dirty_async_ratio to 30.  Or use write-and-fsync
from http://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz with
the `-f' option.

I don't know why the read bandwidth appears to be lower.  Try increasing
the readahead with `blockdev --setra'?

  reply	other threads:[~2004-04-02 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02 15:41 Timothy Miller
2004-04-02 23:47 ` Andrew Morton [this message]
2004-04-05 15:14   ` Timothy Miller

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=20040402154718.43f16ea9.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miller@techsource.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

all inboxes | Powered by JetHome®