Re: gvinum raid5 performance seems slow
- From: "R. B. Rid***" <arne_woerner@xxxxxxxxx>
- Date: Sun, 29 Oct 2006 23:05:32 -0800 (PST)
--- Greg 'groggy' Lehey <grog@xxxxxxxxxxx> wrote:
"Sufficiently large data blocks" equates to several megabytes.I did it that way in my graid5 class:
Currently MAXPHYS, the largest transfer request that would get to the
bio layer, is 131072 bytes. This would imply a stripe size of not
more than 32 kB for a five disk array, which is unrealistically small.
I did consider this optimization, but it would only work if Vinum were
first to buffer multiple requests, and there are all sorts of
reliability issues there. For example, you'd have to lie about the
first few requests that were only buffered and not actually sent out
to disk. Possibly it should be done anyway.
http://home.tiscali.de/cmdr_faako/geom_raid5.tbz
The source might look somehow incomprehensible, but it seems to be quite stable
(on amd64 and i386)...
I tried to benchmark with a 3 disk array:
Single disk: 30MB/sec write speed
graid5 device: 20MB/sec write speed
I would be interested in other benchmarks about it.
-Arne
____________________________________________________________________________________
Get your email and see which of your friends are online - Right on the New Yahoo.com
(http://www.yahoo.com/preview)
_______________________________________________
freebsd-performance@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-performance
To unsubscribe, send any mail to "freebsd-performance-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: gvinum raid5 performance seems slow
- From: Greg 'groggy' Lehey
- Re: gvinum raid5 performance seems slow
- References:
- Re: gvinum raid5 performance seems slow
- From: Greg 'groggy' Lehey
- Re: gvinum raid5 performance seems slow
- Prev by Date: Re: gvinum raid5 performance seems slow
- Next by Date: Re: gvinum raid5 performance seems slow
- Previous by thread: Re: gvinum raid5 performance seems slow
- Next by thread: Re: gvinum raid5 performance seems slow
- Index(es):