X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.192]) by svr1.postgresql.org (Postfix) with ESMTP id 53C59D1C4C8 for ; Mon, 21 Jul 2003 10:04:55 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr4.postgresql.org [64.117.224.192]) (amavisd-new, port 10024) with ESMTP id 70823-06 for ; Mon, 21 Jul 2003 10:04:53 +0000 (GMT) Received: from cerebro.int-bytecraft.com (unknown [219.93.229.26]) by svr1.postgresql.org (Postfix) with ESMTP id 82C73D1C4C7 for ; Mon, 21 Jul 2003 07:04:51 -0300 (ADT) Received: from bytecraft.com.my (home.int-bytecraft.com [127.0.0.1]) by cerebro.int-bytecraft.com (8.11.6/8.11.6) with ESMTP id h6LA1LA16718; Mon, 21 Jul 2003 18:01:22 +0800 Message-ID: <3F1BBBD3.6070405@bytecraft.com.my> Date: Mon, 21 Jul 2003 18:09:23 +0800 From: Ang Chin Han User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: shridhar_daithankar@persistent.co.in Cc: Alexander Priem , pgsql-performance@postgresql.org Subject: Re: Tuning PostgreSQL References: <3F1C00B2.20319.147235A4@localhost> In-Reply-To: <3F1C00B2.20319.147235A4@localhost> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF96D9C786CF7C34E614F978A" X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/325 X-Sequence-Number: 2618 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF96D9C786CF7C34E614F978A Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Shridhar Daithankar wrote: > On 21 Jul 2003 at 11:23, Alexander Priem wrote: >>I use ext3 filesystem, which probably is not the best performer, is it? > > No. You also need to check ext2, reiser and XFS. There is no agreement between > users as in what works best. You need to benchmark and decide. Need? Maybe I'm a bit disillusioned, but are the performances between the filesystems differ so much as to warrant the additional effort? (e.g. XFS doesn't come with Red Hat 9 -- you'll have to patch the source, and compile it yourself). Benchmarking it properly before deployment is tough: are the test load on the db/fs representative of actual load? Is 0.5% reduction in CPU usage worth it? Did you test for catastrophic failure by pulling the plug during write operations (ext2) to test if the fs can handle it? Is the code base for the particular fs stable enough? Obscure bugs in the fs? For the record, we tried several filesystems, but stuck with 2.4.9's ext3 (Red Hat Advanced Server). Didn't hit a load high enough for the filesystem choices to matter after all. :( -- Linux homer 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux 5:30pm up 207 days, 8:35, 5 users, load average: 5.33, 5.16, 5.21 --------------enigF96D9C786CF7C34E614F978A Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/G7vVNYbTUIgzwfARAoDaAJ48oC9cSnTNx6KxdMy+0eSw5rK3YQCggQ9H JvL8onI2xgHgc2/hyCmNpCQ= =ISi4 -----END PGP SIGNATURE----- --------------enigF96D9C786CF7C34E614F978A--