public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Daniel Blueman <daniel.blueman@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File system performance, hardware performance, ext3, 3ware RAID1, etc.
Date: Fri, 13 Feb 2004 17:56:40 -0500	[thread overview]
Message-ID: <402D5628.6070705@techsource.com> (raw)
In-Reply-To: <9792.1076675029@www11.gmx.net>



Daniel Blueman wrote:
> Willy Tarreau <willy@w.ods.org> wrote in message
> news:<1oEGw-2ex-1@gated-at.bofh.it>...
> 
>>On Thu, Feb 12, 2004 at 06:32:31PM -0500, Timothy Miller wrote:
>> 
>>
>>>For writes, iozone found an upper bound of about 10megs/sec, which is 
>>>abysmal.  Typically, I'd expect writes to be faster (on a single drive) 
>>>than reads, because once the write is sent, you can forget about it. 
>>>You don't have to wait around for something to come back, and that 
>>>latency for reads can hurt performance.  The OS can also buffer writes 
>>>and reorder them in order to improve efficiency.
>>
>>It depends on the disk too. Lots of disks (specially IDE) are far slower
>>on writes than they are on reads.
> 
> 
> No. Have you verified this? If you 'dd' your swap partition from /dev/zero
> on IDE, you'll see write performance closely matches read performance, for
> drives old and new.
> 

And this sort of things is what I find with raw writes to the model of 
drive I'm using.  However, it seems that there must be some issue with 
the 3ware 7000-2 which is killing performance, or the way the Linux 
kernel is dealing with this sorta-SCSI device.

The WD1200JB should get like 30-40 megs/sec, but when being accessed 
through the 3ware, I get 10-16 megs/sec.

What could the 3ware be doing?


  parent reply	other threads:[~2004-02-13 22:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 12:23 File system performance, hardware performance, ext3, 3ware RAID1, etc Daniel Blueman
2004-02-13 14:27 ` Jamie Lokier
2004-02-13 14:44   ` Daniel Blueman
2004-02-13 16:15     ` Bartlomiej Zolnierkiewicz
2004-02-13 22:56 ` Timothy Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-14 18:16 Walt H
2004-02-16 17:53 ` Timothy Miller
2004-02-12 23:32 Timothy Miller
2004-02-13  5:53 ` Willy Tarreau
2004-02-13 19:19   ` Timothy Miller
2004-02-13 22:39     ` Willy Tarreau
2004-02-13 23:14       ` Timothy Miller
2004-02-13 19:30   ` Eric D. Mudama
2004-02-13 19:55     ` Linus Torvalds
2004-02-13 20:44       ` John Bradford
2004-02-13 22:45       ` Willy Tarreau

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=402D5628.6070705@techsource.com \
    --to=miller@techsource.com \
    --cc=daniel.blueman@gmx.net \
    --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