Date: Mon, 30 Oct 2006 15:49:13 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Petri Helenius <pete@he.iki.fi> Cc: Steve Peterson <stevep-hv@zpfe.com>, performance@freebsd.org Subject: Re: gvinum raid5 performance seems slow Message-ID: <20061030051913.GG1052@wantadilla.lemis.com> In-Reply-To: <45458981.8010302@he.iki.fi> References: <6.2.3.4.0.20061027180329.020bed68@localhost> <4542D941.2070204@centtech.com> <6.2.3.4.0.20061028124559.02105930@localhost> <4543AD35.30205@he.iki.fi> <20061030013211.GC1052@wantadilla.lemis.com> <45458981.8010302@he.iki.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
--xjyYRNSh/RebjC6o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 30 October 2006 at 7:11:29 +0200, Petri Helenius wrote: > Greg 'groggy' Lehey wrote: >> >> Single stream tests aren't very good examples for RAID-5, because it >> performs writes in two steps: first it reads the old data, then it >> writes the new data. > > If it really does it this way, instead doing write-only when writing > sufficiently large blocks, that would explain the performance due to > double rotational latency wait for each stripe size. No, this works at the bio layer, where everything is cushioned on buffer cache. > Most implementations also use read/write caches to optimize this > even further. "Sufficiently large data blocks" equates to several megabytes. 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. Greg -- See complete headers for address and phone numbers. --xjyYRNSh/RebjC6o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFFRYtRIubykFB6QiMRAsL3AJ93edVFQOlzRExsHe3X7nsqLn3qqQCfanSO Ri9z3PrrDgWp2j/O8+yMhCM= =opGf -----END PGP SIGNATURE----- --xjyYRNSh/RebjC6o--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061030051913.GG1052>