Re: RAID 5 stripe size regarding new install




If the stripe size is configurable, choosing the right stripe size is
important. A stripe size that is too small can split an otherwise
single I/O across multiple disk drives, causing multiple seeks to occur
when one drive could satisfy the I/O. Under Windows 2000 the largest I/O
that is supported is 64-KB, so we recommend using the 64-KB stripe size
whenever possible.



--
supafly
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message113358.html

.



Relevant Pages

  • Re: Raid 5 performance
    ... Which stripe size to use with a RAID controller depends ... >> other and possibly unrelated disk operations at the same time. ... > on every combination I've ever used when it comes to sequential I/O. ...
    (freebsd-performance)
  • SQL Server 2000 Corrupt Database/file
    ... Getting I/O (Torn Page) Error on my User DB. ... My Drive E: as Stripe ... Please let me know beter way to do. ...
    (microsoft.public.sqlserver)
  • Database corrupt or Database file corrupt
    ... Getting I/O (Torn Page) Error on my User DB. ... My Drive E: as Stripe ... Please let me know beter way to do. ...
    (microsoft.public.sqlserver)
  • Re: Buffered I/O slowness
    ... > o one I/O thread per disk, round robined across the 8 CPUs ... It had 64 disks with a 64k stripe unit (XFS was made aware of this ... but it looks like both the readahead and regular buffered ...
    (Linux-Kernel)