linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Nelson" <jnelson-linux-raid@jamponi.net>
To: David Lethe <david@santools.com>
Cc: Keld J?rn Simonsen <keld@dkuug.dk>,
	Matt Garman <matthew.garman@gmail.com>,
	linux-raid@vger.kernel.org
Subject: Re: new bottleneck section in wiki
Date: Thu, 3 Jul 2008 07:28:57 -0500	[thread overview]
Message-ID: <cccedfc60807030528t4724cbdhe5334ed0acefc536@mail.gmail.com> (raw)
In-Reply-To: <A20315AE59B5C34585629E258D76A97CF200D3@34093-C3-EVS3.exchange.rackspace.com>

> Not true, Jon.  The test above was limited by the amount of data that a
> single drive head can push to the controller with 100% sequential reads
> of 64KB.  You can't say anything about chipset bottlenecks, because you
> haven't created a condition where the chipset could even be a
> bottleneck.  I/O is constrained by the disk drives.
>
> Now, if you attached industrial class SSDs that operate at media speeds
> with access time in the NS range, then you could be in a position to
> benchmark chipset performance.

Well, that's true. However, perhaps I mis-spoke. What I was intending
on doing is showing that the chipset was /not/ the limiting factor
here, not checking it's maximum speed, but rather given what I know
about the drives individually, and then what the rates are with all
drives cookin', then I can say, "Well, at least the chipset or bus
aren't getting in the way." Note that I also added "or bus" to my
statement. Would you say that this statement is more accurate or am I
getting the terminology wrong, again?


-- 
Jon

  reply	other threads:[~2008-07-03 12:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 15:56 new bottleneck section in wiki Keld Jørn Simonsen
2008-07-02 16:43 ` Justin Piszcz
2008-07-02 17:21   ` Keld Jørn Simonsen
2008-07-02 17:04 ` David Lethe
2008-07-02 17:51   ` Keld Jørn Simonsen
2008-07-02 18:08     ` David Lethe
2008-07-02 18:26       ` Keld Jørn Simonsen
2008-07-02 21:55         ` Roger Heflin
2008-07-02 19:45       ` Matt Garman
2008-07-02 20:05         ` Keld J?rn Simonsen
2008-07-02 20:24         ` Richard Scobie
2008-07-02 19:03   ` Matt Garman
2008-07-02 19:10     ` Jon Nelson
2008-07-02 19:35       ` Keld J?rn Simonsen
2008-07-02 19:38         ` Jon Nelson
2008-07-02 22:07           ` David Lethe
2008-07-03 12:28             ` Jon Nelson [this message]
2008-07-03 14:00               ` Justin Piszcz
2008-07-02 19:17     ` Robin Hill
2008-07-02 19:39     ` Keld J?rn Simonsen
2008-07-03  5:10     ` Doug Ledford
2008-07-02 21:45   ` Roger Heflin
2008-07-02 17:33 ` Iustin Pop
2008-07-02 18:14   ` Keld Jørn Simonsen

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=cccedfc60807030528t4724cbdhe5334ed0acefc536@mail.gmail.com \
    --to=jnelson-linux-raid@jamponi.net \
    --cc=david@santools.com \
    --cc=keld@dkuug.dk \
    --cc=linux-raid@vger.kernel.org \
    --cc=matthew.garman@gmail.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;
as well as URLs for NNTP newsgroup(s).