Date: Wed, 20 Apr 2005 10:17:31 +0200 From: Claus Guttesen <kometen@gmail.com> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-performance@freebsd.org Subject: Re: some simple nfs-benchmarks on 5.4 RC2 Message-ID: <b41c75520504200117608f8e31@mail.gmail.com> In-Reply-To: <42650EB2.4040409@centtech.com> References: <b41c75520504190418308f94cc@mail.gmail.com> <4264EC60.3020600@centtech.com> <b41c75520504190443187617de@mail.gmail.com> <4264EF40.3060900@centtech.com> <b41c75520504190455542071f7@mail.gmail.com> <4264F8A8.3080405@centtech.com> <b41c755205041906145fc4719c@mail.gmail.com> <426507DC.50409@centtech.com> <b41c7552050419065519057cb2@mail.gmail.com> <42650EB2.4040409@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> >>I think you are disk bound.. You should not be disk bound at this poin= t with a > >>good RAID controller.. > > Good point, it's an atabeast from nexsan. > Looks like they are indeed waiting on disk.. You could try making two 6 d= isk > raid5 in your controller, then striping those with vinum. That might hel= p. > Possibly, if your controller supports it, setting up the array as JBOD, a= nd then > use vinum to build your raid 5 (not sure if it will be faster or not). I had a raid 5 volume with 5 disks (1.6 TB) and did the same dd: elin% dd if=3D/dev/zero of=3D/nfssrv/dd.tst bs=3D1024 count=3D1048576 1048576+0 records in 1048576+0 records out 1073741824 bytes transferred in 21.373114 secs (50237968 bytes/sec) The dd on the other raid-volume (12 disks) did also comlete in approx. 22 sec. So no difference when I lower the number of disks in an array. Frame size on the storage-device is 2112 (bytes). regards Claus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b41c75520504200117608f8e31>