G
Guest
Guest
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)
In article <Na4Gc.193628$Gx4.142602@bgtnsc04-news.ops.worldnet.att.net>,
ron-reaugh@worldnet.att.net says...
>
> "Leythos" <void@nowhere.com> wrote in message
> news:MPG.1b528c1ef34106a298a755@news-server.columbus.rr.com...
> > In article <Xo1Gc.60325$OB3.45145@bgtnsc05-news.ops.worldnet.att.net>,
> > ron-reaugh@worldnet.att.net says...
> > > In fact usually a stripe size of
> > > 16K or 32k for two drives is usually optimal. Also Anand doesn't seem
> to
> > > understand the definition of what a stripe is.
> >
> > Stripe size is optimal based on the type of data being accessed, which,
> > as most people tend to overgeneralise, is different based on what the
> > primary function is for the system.
> >
> > As an example:
> >
> > 1) Database - larger stripes are better
>
> Wrong. Stripe units 2x-3x the average record size is optimal.
>
> > 2) Large images or other LARGE files - larger is better
>
> Wrong, The stripe size that optimizes sustained transfer rate is best here
> and often that's NOT large stripe size.
>
> > 3) Most home (non-soho/non business) systems - smaller
> > 4) Video editing - larger
>
> No.
>
> > 5) Web Page Design - smaller
> > 6) Games - smaller
> >
> > And the list goes on.
>
> And you make these up how?
I'm not sure how to reply to you without ticking you off, but you are
wrong, larger average file sizes means larger stripe sizes for better
performance, which is exactly what I wrote.
--
--
spamfree999@rrohio.com
(Remove 999 to reply to me)
In article <Na4Gc.193628$Gx4.142602@bgtnsc04-news.ops.worldnet.att.net>,
ron-reaugh@worldnet.att.net says...
>
> "Leythos" <void@nowhere.com> wrote in message
> news:MPG.1b528c1ef34106a298a755@news-server.columbus.rr.com...
> > In article <Xo1Gc.60325$OB3.45145@bgtnsc05-news.ops.worldnet.att.net>,
> > ron-reaugh@worldnet.att.net says...
> > > In fact usually a stripe size of
> > > 16K or 32k for two drives is usually optimal. Also Anand doesn't seem
> to
> > > understand the definition of what a stripe is.
> >
> > Stripe size is optimal based on the type of data being accessed, which,
> > as most people tend to overgeneralise, is different based on what the
> > primary function is for the system.
> >
> > As an example:
> >
> > 1) Database - larger stripes are better
>
> Wrong. Stripe units 2x-3x the average record size is optimal.
>
> > 2) Large images or other LARGE files - larger is better
>
> Wrong, The stripe size that optimizes sustained transfer rate is best here
> and often that's NOT large stripe size.
>
> > 3) Most home (non-soho/non business) systems - smaller
> > 4) Video editing - larger
>
> No.
>
> > 5) Web Page Design - smaller
> > 6) Games - smaller
> >
> > And the list goes on.
>
> And you make these up how?
I'm not sure how to reply to you without ticking you off, but you are
wrong, larger average file sizes means larger stripe sizes for better
performance, which is exactly what I wrote.
--
--
spamfree999@rrohio.com
(Remove 999 to reply to me)