public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Blueman" <daniel.blueman@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: File system performance, hardware performance, ext3, 3ware RAID1, etc.
Date: Fri, 13 Feb 2004 13:23:49 +0100 (MET)	[thread overview]
Message-ID: <9792.1076675029@www11.gmx.net> (raw)

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.

In the case of small transfers, the drive can hand them off to the on-drive
write cache (2/8MB usually). The only case where IDE disks will be 'slow' for
write performance is where you have no disk I/O scheduling and lots of small
reads/writes - this case wins on SCSI, but many modern IDE disks and
controllers also have tagged command queuing, so it is even more of a corner case.

Dan

-- 
Daniel J Blueman

GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...)
jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++


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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 12:23 Daniel Blueman [this message]
2004-02-13 14:27 ` File system performance, hardware performance, ext3, 3ware RAID1, etc Jamie Lokier
2004-02-13 14:44   ` Daniel Blueman
2004-02-13 16:15     ` Bartlomiej Zolnierkiewicz
2004-02-13 22:56 ` Timothy Miller
  -- 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=9792.1076675029@www11.gmx.net \
    --to=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