Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 3E1346337E0 for ; Fri, 10 Apr 2009 14:40:51 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 12792-02 for ; Fri, 10 Apr 2009 14:40:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from EXHUB018-2.exch018.msoutlookonline.net (exhub018-2.exch018.msoutlookonline.net [64.78.17.17]) by mail.postgresql.org (Postfix) with ESMTP id 70B826335AF for ; Fri, 10 Apr 2009 14:40:49 -0300 (ADT) Received: from EXVMBX018-1.exch018.msoutlookonline.net ([64.78.17.47]) by EXHUB018-2.exch018.msoutlookonline.net ([64.78.17.17]) with mapi; Fri, 10 Apr 2009 10:40:47 -0700 From: Scott Carey To: Josh Berkus CC: henk de wit , "jesper@krogh.cc" , "pgsql-performance@postgresql.org" Date: Fri, 10 Apr 2009 10:40:46 -0700 Subject: Re: Using IOZone to simulate DB access patterns Thread-Topic: [PERFORM] Using IOZone to simulate DB access patterns Thread-Index: Acm6AjoTcuyAGHMtTIGKC4PeJcHFkgAAUBwT Message-ID: In-Reply-To: <49DF8277.4050801@agliodbs.com> Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200904/201 X-Sequence-Number: 33568 On 4/10/09 10:31 AM, "Josh Berkus" wrote: > Scott, >=20 >> 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 -- wi= th >> surprising and useful tuning results. Forcing a cache flush or sync bef= ore >> 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. >=20 > 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 a= s well. " fio is an I/O tool meant to be used both for benchmark and stress/hardwar= e 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 wel= l 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" >=20 >=20 > -- > Josh Berkus > PostgreSQL Experts Inc. > www.pgexperts.com >=20