From: Jeremy Higdon <jeremy@classic.engr.sgi.com>
To: Simon Trimmer <simon@urbanmyth.org>, Mukul Kotwani <mkotwani@yahoo.com>
Cc: Craig Tierney <ctierney@hpti.com>, linux-scsi@vger.kernel.org
Subject: Re: Performance
Date: Sat, 3 Aug 2002 23:27:45 -0700 (PDT) [thread overview]
Message-ID: <10208032327.ZM1350371@classic.engr.sgi.com> (raw)
In-Reply-To: Simon Trimmer <simon@urbanmyth.org> "Re: Performance" (Aug 3, 7:16pm)
We've seen about 15000 IOPS from a 2200 and nearly 40000 from a 2310.
With the proper test and proper hardware, you ought to see up to 102 MB/s
on disk reads with a 2200 and 204 MB/s with the 2300 (10^6 MB).
However, you may have trouble matching this in the Linux block layer.
Perhaps if you try the sg driver with direct I/O . . . .
I question the 100% random results that you got from Windows. 100%
random implies no cache hits, which would leave you with the raw
IOPS that the drive can supply (260 sounds in the right ballpark).
It would be impossible for the drive to supply 7000 IOPS in a
random workload. If you were supplying out of the drive cache or
Windows cache, then 7000 seems more reasonable (though perhaps not
a very interesting number).
jeremy
next prev parent reply other threads:[~2002-08-04 6:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 0:22 Max IO size Mukul Kotwani
2002-08-01 8:45 ` Jens Axboe
2002-08-01 23:54 ` Mukul Kotwani
2002-08-02 5:17 ` Mukul Kotwani
2002-08-02 6:39 ` Jens Axboe
2002-08-02 6:44 ` Jens Axboe
2002-08-02 6:55 ` Mukul Kotwani
2002-08-02 7:50 ` Performance Mukul Kotwani
2002-08-02 9:16 ` Performance Fabien Salvi
2002-08-02 14:16 ` Performance Craig Tierney
2002-08-02 23:01 ` Performance Mukul Kotwani
2002-08-02 23:06 ` Performance Randy.Dunlap
2002-08-03 8:26 ` Performance Mukul Kotwani
2002-08-03 16:34 ` Performance Randy.Dunlap
2002-08-03 18:16 ` Performance Simon Trimmer
2002-08-03 20:03 ` Performance Mukul Kotwani
2002-08-04 6:27 ` Jeremy Higdon [this message]
2002-08-04 7:39 ` Performance Mukul Kotwani
2002-08-04 8:01 ` Performance Jeremy Higdon
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=10208032327.ZM1350371@classic.engr.sgi.com \
--to=jeremy@classic.engr.sgi.com \
--cc=ctierney@hpti.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mkotwani@yahoo.com \
--cc=simon@urbanmyth.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