public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Higdon <jeremy@classic.engr.sgi.com>
To: Mukul Kotwani <mkotwani@yahoo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Performance
Date: Sun, 4 Aug 2002 01:01:58 -0700 (PDT)	[thread overview]
Message-ID: <10208040101.ZM1331778@classic.engr.sgi.com> (raw)
In-Reply-To: Mukul Kotwani <mkotwani@yahoo.com> "Re: Performance" (Aug  4, 12:39am)

On Aug 4, 12:39am, Mukul Kotwani wrote:
> 
> Thanks for the reply Jeremy!
> 
> Can you point me to the proper test which I can use to
> test it? I think I have pretty good servers and
> storage. What did u guys use..and was there any tuning
> of the OS required?
> 
> For the IOPs, I guess it must have been the Windows
> cache then, because ths storage used was the same in
> both cases.
> 
> Mukul


Well, a later post from you indicated you were using 13 luns
(I presume that means 13 of these 15K drives).  That would
be 538 IOPS per drive, which sounds a little high (2ms per
I/O would account for 1/2 rotation and no seek/settle time).

The tests we've run were not using stock Linux SCSI, so it
might be hard for you to duplicate.  Have you tried using
the raw driver interface to sd (/dev/raw), or the sg
benchmark tools?  I believe the raw interface should give
your the IOPS and the sg interface would give you the MB/s
(and also the IOPS perhaps).

A couple of years ago, we had some patches to the raw interface
and block layer that allowed kiobufs to be passed directly to
the SCSI interface.  That was nice because we avoided the
CPU overhead of deconstruction and reconstruction of large
I/O requests.  However, it was messy.  I believe that the
2.5 changes with bio should help a lot in this area, without
the mess.

jeremy

      reply	other threads:[~2002-08-04  8:01 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                 ` Performance Jeremy Higdon
2002-08-04  7:39                   ` Performance Mukul Kotwani
2002-08-04  8:01                     ` Jeremy Higdon [this message]

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=10208040101.ZM1331778@classic.engr.sgi.com \
    --to=jeremy@classic.engr.sgi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mkotwani@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox