From: TJ <systemloc@earthlink.net>
To: linux-raid@vger.kernel.org
Subject: Re: Looking for the cause of poor I/O performance
Date: Sun, 5 Dec 2004 10:17:13 -0500 [thread overview]
Message-ID: <200412051017.13228.systemloc@earthlink.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0412041809530.21262-100000@coffee.psychology.mcmaster.ca>
> for comparison, a fairly crappy SiS 735-based k7 system with
> 64b-wide PC2100 can deliver maybe 1.2 GB/s dram bandwidth.
> hdparm -T is about 500 MB/s, and would probably have trouble
> breaking 200 MB/s with raid0 even if it had enough buses.
>
> an older server of mine is e7500-based, dual xeon/2.4's, with
> 2xPC1600 ram. it sustains about 1.6 GB/s on Stream, and about
> 500 MB/s hdparm -T, and can sustain 250 MB/s through it's 6-disk
> raid without any problem.
hmmm.. In these cases, how does the throughput exceed the PCI bandwidth? Do
these boards have multiple busses? PCI-X?
TJ Harrell
next prev parent reply other threads:[~2004-12-05 15:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 16:38 Looking for the cause of poor I/O performance TJ
2004-12-03 0:49 ` Mark Hahn
2004-12-03 3:54 ` Guy
2004-12-03 6:33 ` TJ
2004-12-03 7:38 ` Guy
2004-12-04 15:23 ` TJ
2004-12-04 17:59 ` Guy
2004-12-04 23:51 ` Mark Hahn
2004-12-05 1:00 ` Steven Ihde
2004-12-06 17:48 ` Steven Ihde
2004-12-06 19:29 ` Guy
2004-12-06 21:10 ` David Greaves
2004-12-06 23:02 ` Guy
2004-12-08 9:24 ` David Greaves
2004-12-08 18:31 ` Guy
2004-12-08 22:00 ` Steven Ihde
2004-12-08 22:25 ` Guy
2004-12-08 22:41 ` Guy
2004-12-09 1:40 ` Steven Ihde
2004-12-12 8:56 ` [linux-lvm] Re: Looking for the cause of poor I/O performance - a test script David Greaves
2004-12-12 8:56 ` David Greaves
2004-12-28 0:13 ` [linux-lvm] " Steven Ihde
2004-12-28 0:13 ` Steven Ihde
2004-12-06 21:16 ` Looking for the cause of poor I/O performance Steven Ihde
2004-12-06 21:42 ` documentation of /sys/vm/max-readahead Morten Sylvest Olsen
2004-12-05 2:16 ` Looking for the cause of poor I/O performance Guy
2004-12-05 15:14 ` TJ
2004-12-06 21:39 ` Mark Hahn
2004-12-05 15:17 ` TJ [this message]
2004-12-06 21:34 ` Mark Hahn
2004-12-06 23:06 ` Guy
2004-12-03 6:51 ` TJ
2004-12-03 20:03 ` TJ
2004-12-04 22:59 ` Mark Hahn
2004-12-03 7:12 ` TJ
-- strict thread matches above, loose matches on Subject: below --
2004-12-03 11:30 TJ
2004-12-03 11:46 ` Erik Mouw
2004-12-03 15:09 ` TJ
2004-12-03 16:25 ` Erik Mouw
2004-12-03 16:32 ` David Greaves
2004-12-03 16:50 ` Guy
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=200412051017.13228.systemloc@earthlink.net \
--to=systemloc@earthlink.net \
--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.