Date: Fri, 13 Jun 2008 09:01:30 -0500 From: David Kelly <dkelly@hiwaay.net> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: FreeBSD Questions <questions@freebsd.org>, freebsd-questions@freebsd.org Subject: Re: Stripe sizes with gstripe Message-ID: <20080613140130.GA8616@Grumpy.DynDNS.org> In-Reply-To: <20080613090714.K4713@wojtek.tensor.gdynia.pl> References: <200806121521.16237.kirk@strauser.com> <F67BB207-BA27-4772-A90C-5CB3279F0172@hiwaay.net> <20080613090714.K4713@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 13, 2008 at 09:08:48AM +0200, Wojciech Puchar wrote: > >>Does gstripe read an entire stripe at a time? If so, why do that instead > >>of > >>just reading a few requested blocks? If not, then is there any advantage > >>to large stripes? > > > >Apparently it won't read anything larger than your stripe size which > >defaults to a miserable 4k. > > > depending from what's needed, but unless i need just huge linear transfer, > i set stripe size to something huge, like 256MB. > > then single read is rarely split on 2 disks, while multiple reads have > good chances to touch different drives Come to think of it I didn't try setting the stripe size larger than the ATA max transaction size of 128k. Still, I don't understand what is going on when I use md5(1) on a gigabyte file hosted on a gstripe partition with 128k stripes that "systat -v" reports transactions are usually between 42k and 43k each? On a non-striped filesystem the same operation runs 126k to 127k transfers. Transfer bandwidth seems to be limited by the number of transactions per second more than the size of the transaction. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080613140130.GA8616>