From: "Donghui Wen" <dhwen@protegonetworks.com>
To: Joshua Baker-LePain <jlb17@duke.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: 3ware bad write speed.
Date: Mon, 24 Mar 2003 11:49:57 -0800 [thread overview]
Message-ID: <004501c2f23e$8c2b5760$df01010a@moon> (raw)
In-Reply-To: Pine.LNX.4.44.0303240912080.2059-100000@chaos.egr.duke.edu
Thanks! Joshua:
We are runing oracle on rehat advanced server 2.1. Oracle only certified
this version of redhat with ext2. That' why we could not switch to another
linux
or file system. :-(
Donghui
> The card is capable of much better than that. Here are my numbers from a
> 7 disk RAID5 array (8th is a hot spare) on a 7500-8 board:
>
> Sequential Writes
> File Blk Num Avg
> Maximum
> Lat% Lat% CPU
> Identifier Size Size Thr Rate (CPU%) Latency
> Latency
> >2s >10s Eff
> ---------------------------- ------ ----- --- ------ ------ ---------
> ---------
> -- -------- -------- -----
> 2.4.18-17SGI_XFS_1.2pre3smp 4096 4096 1 49.50 20.52% 0.068
> 2915.
> 71 0.00124 0.00000 241
> 2.4.18-17SGI_XFS_1.2pre3smp 4096 4096 2 45.17 23.21% 0.141
> 7873.
> 45 0.00343 0.00000 195
> 2.4.18-17SGI_XFS_1.2pre3smp 4096 4096 4 39.98 23.29% 0.335
> 13338.
> 23 0.00887 0.00010 172
> 2.4.18-17SGI_XFS_1.2pre3smp 4096 4096 8 39.23 24.30% 0.631
> 7887.
> 96 0.01535 0.00000 161
>
> Obviously I've got more spindles, but your speeds shouldn't be *that* bad.
> Some things to check:
>
> 1) You said latest drivers, but make sure that you upgraded everything --
> a driver set from 3ware is driver+firmware+3dm. Specifically, make sure
> your firmware is up to date with your driver.
>
> 2) Make sure that your kernel supports HIGHIO. I don't know if that
> enterprise kernel does (do you need to run it?), but it makes a *big*
> difference. The latest 3ware drivers support HIGHIO, but the kernel needs
> to as well.
>
> 3) Make sure your drives are listed as compatible.
>
> 4) Try a different FS. The numbers above are with XFS -- with ext3 I was
> getting write speeds of only half that (at best).
>
> Good luck.
>
> --
> Joshua Baker-LePain
> Department of Biomedical Engineering
> Duke University
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2003-03-24 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 20:45 3ware bad write speed Donghui Wen
2003-03-24 14:18 ` Joshua Baker-LePain
2003-03-24 19:49 ` Donghui Wen [this message]
2003-03-26 0:40 ` Stephan van Hienen
2003-03-26 15:55 ` Joshua Baker-LePain
2003-04-02 7:20 ` Christian Diehl
-- strict thread matches above, loose matches on Subject: below --
2003-03-22 21:07 Rechenberg, Andrew
2003-03-22 21:36 ` Donghui Wen
2003-03-22 23:34 Rechenberg, Andrew
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='004501c2f23e$8c2b5760$df01010a@moon' \
--to=dhwen@protegonetworks.com \
--cc=jlb17@duke.edu \
--cc=linux-raid@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 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.