All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bill Rugolsky Jr." <rugolsky@ead.dsa.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, lm@bitmover.com, jgiglio@smythco.com
Subject: Re: 3ware discontinuing the Escalade Series
Date: Fri, 5 Oct 2001 14:22:15 -0400	[thread overview]
Message-ID: <20011005142215.C1221@ead45> (raw)
In-Reply-To: <20011005125259.B1221@ead45> <E15pYQ1-00071M-00@the-village.bc.nu>
In-Reply-To: <E15pYQ1-00071M-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Oct 05, 2001 at 06:05:49PM +0100

On Fri, Oct 05, 2001 at 06:05:49PM +0100, Alan Cox wrote:
> > I really like my 7800.  At this point I guess I'm going to convert from
> > hard to soft RAID, on the theory that (unfixed) bugs in the firmware are less
> > likely to botch JBOD. 
> 
> Except for RAID5 the softraid is also likely to outperform a hardware raid
> controller. With RAID5 its a CPU usage tradeoff

Nod.  I tested both configurations when I first got the cards, and
RAID0 and RAID10 tests with a dual Athlon and the 3ware 7800 showed Linux
soft-RAID outperforming.  I didn't save the hard-RAID results, but the following
is from a private e-mail I sent early in the summer:

RedHat 2.4.5-10smp on dual-Athlon 1.2GHz, 1GB RAM
Soft RAID0 with 4 IBM 41GB 7200RPM ATA-100 drives, chunk size 32K
ext2 w/4K blocks:

Version 1.01c       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
Tyan Thunder    10G 68828  99 138838  75 47756  33 48848  90 116166  61 229.2   1
K7 1.2GHz           ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16  1208 100 +++++ +++ 16883  94  1220 100 +++++ +++  4476  99

I've been using hard-RAID simply because I've been playing with ext3
and LVM, and eliminating MD was one less interaction to worry about until now.

   -Bill Rugolsky

  reply	other threads:[~2001-10-05 18:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04 18:19 3ware discontinuing the Escalade Series Jason Giglio
2001-10-05 16:09 ` Larry McVoy
2001-10-05 16:52   ` rugolsky
2001-10-05 16:56     ` Larry McVoy
2001-10-05 17:05     ` Alan Cox
2001-10-05 18:22       ` Bill Rugolsky Jr. [this message]
2001-10-05 18:39       ` Jeff V. Merkey
  -- strict thread matches above, loose matches on Subject: below --
2001-10-05 16:49 Ryan C. Bonham
2001-10-05 17:05 ` Wilson
2001-10-05 17:13   ` Alan Cox
2001-10-05 17:10 ` Alan Cox
2001-10-05 17:21   ` Joel Jaeggli
2001-10-08 17:38     ` Mike Panetta
2001-10-08 18:38       ` Joel Jaeggli

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=20011005142215.C1221@ead45 \
    --to=rugolsky@ead.dsa.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgiglio@smythco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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 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.