Re: SAME config

David E. Grove wrote:

> I certainly thank you for your explanation, Hans. I appreciate the point
> that it isn't really necessary to agonize over placement of data, indexes,
> etc., and that we can obtain most of the benefit of doing that with a
> simple "one-size-fits-all" scheme which is known to be suboptimal, yet is
> "close" to optimal, and very robust.
>
> I didn't ask my question clearly. I was mainly wondering about the
> meaning
> of "stripe width" in the SAME paper. My first impression is that it means
> the size of the stripe on each individual disk. (Thus, with 6 disks, the
> total stripe size would be 6 MB). It just seemed a little large. But,
> then that is consistent with causing the seek time to be small with
> respect to the transfer time.
>
> Thank you, again.
>

Actually, I found your question quite straight forward. It was also an opportunity to expand of that single point as it does come up from time to time.

Stripe Width:

FRom http://www.webopedia.com/TERM/D/disk_striping.html

"A technique for spreading data over multiple disk drives. Disk striping can speed up operations that retrieve data from disk storage. The computer system breaks a body of data into units and spreads these units across the available disks. Systems that implement disk striping generally allow the user to select the data unit size or stripe width."

I do agree with Jack's response: this question is better directed to SUN/SMCC. Or ask google to 'define RAID stripe width' and look at items like 'Volume Manager With Sun StorEdge ES-310'. Or
http://archive.nlm.nih.gov/pubs/bangbuck/bangbuck.php

/Hans Received on Tue Aug 31 2004 - 12:51:23 CDT