Date: Mon, 09 May 2005 16:08:28 -0400 From: WMC <wc_fbsd@xxiii.com> To: freebsd-questions@freebsd.org Subject: Re: Low HDD tranfer rate with FreeBSD 5.3-Release Message-ID: <6.0.1.1.2.20050509155500.0284c768@mailsvr.xxiii.com> In-Reply-To: <20050509195011.GH38839@dan.emsphone.com> References: <427FA802.90805@chamkila.org> <427FA8CD.8040405@centtech.com> <427FAB5F.6070508@chamkila.org> <427FAF73.7070702@centtech.com> <20050509190245.GF38839@dan.emsphone.com> <427FB663.3090309@chamkila.org> <427FBD12.2090101@chamkila.org> <20050509195011.GH38839@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 03:50 PM 5/9/2005, you wrote:
> > So how does the block size makes the difference?? What is the
> true transfer rate.?
FWIW, there's a nice little disk IO benchmark "Bonnie" available in the
ports & packages. Tests several variations of sequential and random IO. I
don't know how accurate its numbers in absolute terms, but it's at least
good for relative comparisons of devices on similar systems. Be sure to
use the -s option to increase the test file size to something larger than
your ram.
Sample Output:
/datatel > bonnie -s 1000
File './Bonnie.709', size: 1048576000
Writing with putc()...done
Rewriting...done
Writing intelligently...done
Reading with getc()...done
Reading intelligently...done
Seeker 1...Seeker 3...Seeker 2...start 'em...done...done...done...
-------Sequential Output-------- ---Sequential Input--
--Random--
-Per Char- --Block--- -Rewrite-- -Per Char- --Block---
--Seeks---
Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU
1000 10835 98.5 26996 18.1 19876 15.2 8925 83.6 62490 23.0
325.9 3.3
-Wayne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.1.1.2.20050509155500.0284c768>