mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Radford <aradford@3WARE.com>
To: "'Timothy Miller'" <miller@techsource.com>,
	Daniel Blueman <daniel.blueman@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: RE: File system performance, hardware performance, ext3, 3ware RA ID1, etc.
Date: Fri, 13 Feb 2004 15:07:22 -0800	[thread overview]
Message-ID: <A1964EDB64C8094DA12D2271C04B8126F8C92C@tabby> (raw)

Perhaps you are issuing non purely sequential IO.  The card firmware does
some 
reodering, but at some point it will cause performance degradation.  Can you
try 
kernel 2.6 w/xfs? 

Also, in my experience, the 'raw io' interface doesn't issue any
asynchronous IO.  The
card _definately_ needs asynchronous IO posted to it or you will not get
good results
because you won't get all the drives busy.

-Adam

-----Original Message-----
From: Timothy Miller [mailto:miller@techsource.com]
Sent: Friday, February 13, 2004 2:57 PM
To: Daniel Blueman
Cc: linux-kernel@vger.kernel.org
Subject: Re: File system performance, hardware performance, ext3, 3ware
RAID1, etc.




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?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


DISCLAIMER: The information contained in this electronic mail transmission
is intended by 3ware for the use of the named individual or entity to which
it is directed and may contain information that is confidential or
privileged and should not be disseminated without prior approval from 3ware 



             reply	other threads:[~2004-02-13 23:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 23:07 Adam Radford [this message]
2004-02-13 23:52 ` Timothy Miller
2004-02-14 16:25   ` Daniel Blueman
2004-02-16 17:18     ` 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=A1964EDB64C8094DA12D2271C04B8126F8C92C@tabby \
    --to=aradford@3ware.com \
    --cc=daniel.blueman@gmx.net \
    --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®