Re: Using IOZone to simulate DB access patterns

On 4/10/09 10:31 AM, "Josh Berkus" <josh(at)agliodbs(dot)com> wrote:

> Scott,
>
>> FIO with profiles such as the below samples are easy to set up, and they can
>> be mix/matched to test what happens with mixed read/write seq/rand -- with
>> surprising and useful tuning results. Forcing a cache flush or sync before
>> or after a run is trivial. Changing to asynchronous I/O, direct I/O, or
>> other forms is trivial. The output result formatting is very useful as
>> well.
>
> FIO? Link?

First google result:
http://freshmeat.net/projects/fio/

Written by Jens Axobe, the Linux Kernel I/O block layer maintainer. He
wrote the CFQ scheduler and Noop scheduler, and is the author of blktrace as
well.

" fio is an I/O tool meant to be used both for benchmark and stress/hardware
verification. It has support for 13 different types of I/O engines (sync,
mmap, libaio, posixaio, SG v3, splice, null, network, syslet, guasi,
solarisaio, and more), I/O priorities (for newer Linux kernels), rate I/O,
forked or threaded jobs, and much more. It can work on block devices as well
as files. fio accepts job descriptions in a simple-to-understand text
format. Several example job files are included. fio displays all sorts of
I/O performance information. It supports Linux, FreeBSD, and OpenSolaris"

>
>
> --
> Josh Berkus
> PostgreSQL Experts Inc.
> www.pgexperts.com
>