All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: linux-scsi@vger.kernel.org
Cc: Terrence Martin <tmartin@physics.ucsd.edu>
Subject: Re: Write Performance double Read Performance
Date: Tue, 23 Mar 2004 11:28:16 +0000	[thread overview]
Message-ID: <40601F50.F7A85DF0@moving-picture.com> (raw)

Terrence Martin <tmartin@physics.ucsd.edu> wrote:
>
> I have the following system(s)
> 
> Dual 2.8 Ghz Xeon 2U Supermicro Server with 2GB RAM
> Qlogic QLA2310f Controller
> 
> attached to an...
> 
> Infortrend A16F with 16 300GB WD IDE PATA Drives
> The array as a RAID 5 Array with 3 partitions of 1.4TB each. I have 
> mounted one of the partitions to test.
> 
> The OS is....
> 
> Fedora Core 1 with the latest Fedora 2.4 Kernel (2.4.22-1.2174.nptlsmp)
> I have compiled the QLA drivers from the Qlogic site and am using v6.06.10.
> 
> The problem I am noticing is that while doing an IOZone performance test 
> I get nice write performance when the test gets to large files. However 
> my read performance seems to be a little over half my write.   I thought 
> the read should always be faster than the write?

Unfortunately I don't know why, but this is something I've been thinking
of asking as well.

I've seen similar behaviour on a 2.6.3 kernel machine (dual 2.4 Xeons,
2GB RAM) using an external U160 SCSI Chaparral hardware RAID 5 on a
aic79xx controller. I'm using XFS on the RAID.

I've just been using 'lmdd' to/from a 2Gb file - I also see writes about
twice the speed of reads (I'm using the fsync or sync option to lmdd
with the writes).

However, if I increase the readahead on the disk using blockdev from the
default of 256 to 4096, I can get read speeds to be about the same as
the writes.

However, increasing the readahead seems to help this simple streaming
case, but as yet I don't know if it will work in a general file serving
(NFS) situation.

> Before I went down the road of compiling various kernels etc I thought I 
> would post this to linux-scsi to see if it is just some configuration 
> setting to a driver or kernel parameter that needs to be tweaked.  Of 
> course I could be completely reading this wrong but bonnie++ also 
> appears to give similar results and vmstat is similarly low on the read 
> side.

I would also like to know of any optimizations that can be made.

Thanks

James Pearson

             reply	other threads:[~2004-03-23 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 11:28 James Pearson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-22 19:32 Write Performance double Read Performance Terrence Martin

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=40601F50.F7A85DF0@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tmartin@physics.ucsd.edu \
    /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.