X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B6E0152B9E for ; Thu, 14 Jul 2005 10:27:24 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 87068-09 for ; Thu, 14 Jul 2005 13:27:20 +0000 (GMT) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by svr1.postgresql.org (Postfix) with ESMTP id 7B869528C6 for ; Thu, 14 Jul 2005 10:27:19 -0300 (ADT) Received: (qmail 4086 invoked from network); 14 Jul 2005 13:27:22 -0000 Received: from dsl081-060-184.sfo1.dsl.speakeasy.net (HELO noodles) ([64.81.60.184]) (envelope-sender ) by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Jul 2005 13:27:22 -0000 Received: from jwb by noodles with local (Exim 3.36 #1 (Debian)) id 1Dt3kK-0002HH-00; Thu, 14 Jul 2005 06:27:24 -0700 Subject: Re: JFS fastest filesystem for PostgreSQL? From: "Jeffrey W. Baker" To: Dawid Kuroczko Cc: pgsql-performance@postgresql.org In-Reply-To: <758d5e7f05071401034665841c@mail.gmail.com> References: <1121322821.6719.0.camel@noodles> <758d5e7f05071401034665841c@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 14 Jul 2005 06:27:24 -0700 Message-Id: <1121347644.8468.3.camel@noodles> Mime-Version: 1.0 X-Mailer: Evolution 2.3.4 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200507/177 X-Sequence-Number: 13418 On Thu, 2005-07-14 at 10:03 +0200, Dawid Kuroczko wrote: > On 7/14/05, Jeffrey W. Baker wrote: > > [reposted due to delivery error -jwb] > > > > I just took delivery of a new system, and used the opportunity to > > benchmark postgresql 8.0 performance on various filesystems. The system > > in question runs Linux 2.6.12, has one CPU and 1GB of system memory, and > > 5 7200RPM SATA disks attached to an Areca hardware RAID controller > > having 128MB of cache. The caches are all write-back. > > > > I ran pgbench with a scale factor of 1000 and a total of 100,000 > > transactions per run. I varied the number of clients between 10 and > > 100. It appears from my test JFS is much faster than both ext3 and XFS > > for this workload. JFS and XFS were made with the mkfs defaults. ext3 > > was made with -T largefile4 and -E stride=32. The deadline scheduler > > was used for all runs (anticipatory scheduler is much worse). > > > > Here's the result, in transactions per second. > > > > ext3 jfs xfs > > ----------------------------- > > 10 Clients 55 81 68 > > 100 Clients 61 100 64 > > ---------------------------- > > If you still have a chance, could you do tests with other journaling > options for ext3 (journal=writeback, journal=data)? And could you > give figures about performace of other IO elevators? I mean, you > wrote that anticipatory is much wore -- how much worse? :) Could > you give numbers for deadline,anticipatory,cfq elevators? :) > > And, additionally would it be possible to give numbers for bonnie++ > results? To see how does pgbench to bonnie++ relate? Phew, that's a lot of permutations. At 20-30 minutes per run, I'm thinking 5-8 hours or so. Still, for you dear readers, I'll somehow accomplish this tedious feat. As for Bonnie, JFS is a good 60-80% faster than ext3. See my message to ext3-users yesterday. Using bonnie++ with a 10GB fileset, in MB/s: ext3 jfs xfs Read 112 188 141 Write 97 157 167 Rewrite 51 71 60 -jwb