Date: Thu, 19 Feb 2004 23:22:58 -0800 From: David Schultz <das@FreeBSD.ORG> To: mi+mx@aldan.algebra.com Cc: fs@FreeBSD.ORG Subject: Re: strange performance dip shown by iozone Message-ID: <20040220072258.GA17579@VARK.homeunix.com> In-Reply-To: <200402181729.06202@misha-mx.virtual-estates.net> References: <200402181729.06202@misha-mx.virtual-estates.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 18, 2004, mi+mx@aldan.algebra.com wrote: > I'm trying to tune the amrd-based RAID5 and have made several iozone > runs on the array and -- for comparision -- on the single disk connected > to the Serial ATA controller directly. [...] > The filesystems displayed different performance (reads are better with > RAID, writes -- with the single disk), but both have shown a notable dip > in writing (and re-writing) speed when iozone used the record lengthes > of 128 and 256. Can someone explain that? Is that a known fact? How can > that be avoided? This is known as the small write problem for RAID 5. Basically, any write smaller than the RAID 5 stripe size is performed using an expensive read-modify-write operation so that the parity can be recomputed. The solution is to not do that. If you expect lots of small random writes and you can't do anything about it, you need to either use RAID 1 instead of RAID 5, or use a log-structured filesystem, such as NetBSD's LFS.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040220072258.GA17579>