linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Ihde <x-linux-raid@hamachi.dyndns.org>
To: Guy <bugzilla@watkins-home.com>
Cc: 'David Greaves' <david@dgreaves.com>, linux-raid@vger.kernel.org
Subject: Re: Looking for the cause of poor I/O performance
Date: Wed, 8 Dec 2004 17:40:04 -0800	[thread overview]
Message-ID: <20041209014004.GA16666@hamachi.us> (raw)
In-Reply-To: <200412082241.iB8Mfo915469@www.watkins-home.com>

On Wed, 08 Dec 2004 17:41:45 -0500, Guy wrote:
> I also tried changing /proc/sys/vm/max-readahead.
> I tried the default of 31, 0 and 127.  All gave me about the same
> performance.
> 
> I started testing the speed with the dd command below.  It complete in about
> 12.9 seconds.  None of the read ahead changes seem to affect my speed.
> Everything is now set to 0, still 12.9 seconds.
> 12.9 seconds = about 79.38 MB/sec.
> 
> time dd if=/dev/md2 of=/dev/null bs=1024k count=1024

I'm running kernel 2.6.8; I found the readahead setting had a pretty
dramatic effect.  I set readahead for all the drives and their
partitions to zero:

blockdev --setra 0 /dev/{hdc,hdg,sda,hdc5,hdg5,sda5}

I tested various readahead values for the array device by reading 1GB
of data from the device using this procedure:

blockdev --flushbufs /dev/md1
blockdev --setra $readahead /dev/md1
dd if=/dev/md1 of=/dev/null bs=1024k count=1024

These are the results:

RA    transfer rate (B/s)
---------------
   0: 15768513
 128: 33680867
 256: 42982770
 512: 59223248
1024: 78590551
2048: 81918844
4096: 82386839

We seem to reach the point of diminishing returns at 1024 readahead,
~80MB/sec throughput.  To recap, this is with three Seagate Barracuda
drives, two of which are 80GB PATA, the other a 120GB SATA, in a RAID5
configuration.  256 was the default readahead value.  The chunk size
on my array is 32k.  I don't know if that has an effect or not.

-Steve


  reply	other threads:[~2004-12-09  1:40 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 16:38 Looking for the cause of poor I/O performance TJ
2004-12-03  0:49 ` Mark Hahn
2004-12-03  3:54   ` Guy
2004-12-03  6:33     ` TJ
2004-12-03  7:38       ` Guy
2004-12-04 15:23     ` TJ
2004-12-04 17:59       ` Guy
2004-12-04 23:51         ` Mark Hahn
2004-12-05  1:00           ` Steven Ihde
2004-12-06 17:48             ` Steven Ihde
2004-12-06 19:29               ` Guy
2004-12-06 21:10                 ` David Greaves
2004-12-06 23:02                   ` Guy
2004-12-08  9:24                     ` David Greaves
2004-12-08 18:31                       ` Guy
2004-12-08 22:00                         ` Steven Ihde
2004-12-08 22:25                           ` Guy
2004-12-08 22:41                             ` Guy
2004-12-09  1:40                               ` Steven Ihde [this message]
2004-12-12  8:56                               ` Looking for the cause of poor I/O performance - a test script David Greaves
2004-12-28  0:13                                 ` Steven Ihde
2004-12-06 21:16                 ` Looking for the cause of poor I/O performance Steven Ihde
2004-12-06 21:42                   ` documentation of /sys/vm/max-readahead Morten Sylvest Olsen
2004-12-05  2:16           ` Looking for the cause of poor I/O performance Guy
2004-12-05 15:14             ` TJ
2004-12-06 21:39               ` Mark Hahn
2004-12-05 15:17           ` TJ
2004-12-06 21:34             ` Mark Hahn
2004-12-06 23:06               ` Guy
2004-12-03  6:51   ` TJ
2004-12-03 20:03   ` TJ
2004-12-04 22:59     ` Mark Hahn
2004-12-03  7:12 ` TJ
  -- strict thread matches above, loose matches on Subject: below --
2004-12-03 11:30 TJ
2004-12-03 11:46 ` Erik Mouw
2004-12-03 15:09   ` TJ
2004-12-03 16:25     ` Erik Mouw
2004-12-03 16:32   ` David Greaves
2004-12-03 16:50     ` Guy

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=20041209014004.GA16666@hamachi.us \
    --to=x-linux-raid@hamachi.dyndns.org \
    --cc=bugzilla@watkins-home.com \
    --cc=david@dgreaves.com \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).