All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Walt H <waltabbyh@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File system performance, hardware performance, ext3, 3ware RAID1, etc.
Date: Mon, 16 Feb 2004 12:53:38 -0500	[thread overview]
Message-ID: <403103A2.1040709@techsource.com> (raw)
In-Reply-To: <200402141016.51205.waltabbyh@comcast.net>



Walt H wrote:
> 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.
> 
> 
> I'm joining this thread rather late, so perhaps I missed something. What 
> hardware is the test being ran on? I have an AMD MPX based setup which 
> suffers from a chipset bug which effectively limits writes to ~25MB/sec to 
> devices connected via the 768 southbridge. Maybe something similar with your 
> hardware?

Athlon 2800+
Via KT400 chipset (ABIT KD7, I believe)
WD1200JB (Western Digital 120gb)
3ware 7000-2 as RAID1
Latest Red Hat 2.4.20-?? kernel


My wife's computer has the ABIT board with the KT333 and the same drive, 
but not RAID.  SiSoft SANDRA reports 39 megs/sec for writes to an NTFS 
volume.


Right now, I'm thinking the bottleneck may be the 3ware.


  reply	other threads:[~2004-02-16 17:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14 18:16 File system performance, hardware performance, ext3, 3ware RAID1, etc Walt H
2004-02-16 17:53 ` Timothy Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-13 12:23 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
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=403103A2.1040709@techsource.com \
    --to=miller@techsource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=waltabbyh@comcast.net \
    /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.