From: subbie subbie <subbie_subbie@yahoo.com>
To: "Dr. David Alan Gilbert" <dave@treblig.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3Ware 9500S-12 RAID controller -- poor performance
Date: Wed, 5 Oct 2005 06:39:06 -0700 (PDT) [thread overview]
Message-ID: <20051005133906.90687.qmail@web30312.mail.mud.yahoo.com> (raw)
In-Reply-To: <20051005131804.GD18448@gallifrey>
Hi
>
> I've got driver/firmware that is about 2months old
> that
> certainly helped; prior to that I was getting card
> timeouts (although I also upgraded the e1000 driver
> at the same time so it might have been that rather
> than the 3ware that helped).
Two months old might be too old, make sure you have at
least 9.2.1.1
> (Note: I don't expect a driver to perform a
> dangerous
> operation like firmware flashing on boot!)
I believe they are writing to NVRAM or similar so that
makes it much less risky, otherwise they wouldn't have
to write it on each load ... or I might be wrong and
they do it once, not sure.
> > I'm getting a little over 50MB/s when writing to
> my
> > RAID volume when completely idle, there's no
> reason
> > why you should get less.
>
> Well my ~30MB/s is sucking over gig ether and
> writing
> in 10MB chunks; but still 50MB/s for RAID5 feels
> like
> it sucks.
Yes, that's terrible.
Reading the release notes for the latest one, 9.3.0
that also supports their very latest controller,
9550SX, I get the feeling that write performance is
something of an on-going issue with this family of
controllers even though they disguise it in this
latest driver version as a tweak in write
performance.
Another thing, the BBU (battery backup unit) that you
are using was also a can of worms for them so this
makes it even more important for you to upgrade to the
very latest version ,they seem to be having ongoing
issues with that one.
Good luck to us all.
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
next prev parent reply other threads:[~2005-10-05 13:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 6:50 subbie subbie
2005-10-02 0:07 ` Ian Morgan
2005-10-05 6:43 ` subbie subbie
2005-10-05 11:25 ` Dr. David Alan Gilbert
2005-10-05 13:08 ` subbie subbie
2005-10-05 13:18 ` Dr. David Alan Gilbert
2005-10-05 13:39 ` subbie subbie [this message]
2005-10-05 13:40 ` Ian E. Morgan
2005-10-06 7:34 ` subbie subbie
2005-10-03 14:34 ` Ville Herva
2005-10-05 20:07 ` Miquel van Smoorenburg
2005-09-30 6:51 subbie subbie
2005-10-07 21:35 Jon Burgess
2005-10-10 10:42 ` subbie subbie
2005-10-10 10:54 ` Dr. David Alan Gilbert
2005-10-10 11:07 ` Mikael Abrahamsson
2005-10-10 11:22 ` subbie subbie
2005-10-10 12:36 ` Mikael Abrahamsson
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=20051005133906.90687.qmail@web30312.mail.mud.yahoo.com \
--to=subbie_subbie@yahoo.com \
--cc=dave@treblig.org \
--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
all inboxes | Powered by JetHome®