X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id CEACDD1B550 for ; Wed, 27 Aug 2003 23:00:43 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 66759-08 for ; Wed, 27 Aug 2003 20:00:15 -0300 (ADT) Received: from home.samurai.com (home.samurai.com [205.207.28.66]) by svr1.postgresql.org (Postfix) with ESMTP id 44C86D1B8AB for ; Wed, 27 Aug 2003 20:00:12 -0300 (ADT) Received: by home.samurai.com (Postfix, from userid 1014) id 9146D2622F; Wed, 27 Aug 2003 19:00:14 -0400 (EDT) Date: Wed, 27 Aug 2003 19:00:14 -0400 From: Neil Conway To: Shridhar Daithankar Cc: pgsql-performance@postgresql.org Subject: Re: Comparing postgresql7.4 CVS head on linux 2.4.20 and 2.6.0-test4 Message-ID: <20030827230014.GA63737@home.samurai.com> References: <200308272102.26319.shridhar_daithankar@persistent.co.in> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200308272102.26319.shridhar_daithankar@persistent.co.in> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/354 X-Sequence-Number: 3170 On Wed, Aug 27, 2003 at 09:02:25PM +0530, Shridhar Daithankar wrote: > IIRC in a kernel release note recently, it was commented that IO scheduler is > still being worked on and does not perform as much for random seeks, which > exaclty what database needs. Yeah, I've read that as well. It would be interesting to see how 2.6 performs with the traditional (non-anticipatory) scheduler -- I believe you can switch from one I/O scheduler to another via a sysctl. > pgbench -c10 -t100 test1 > tps = 64.917044 (including connections establishing) > tps = 65.438067 (excluding connections establishing) Interesting that the performance of 2.4.20 for this particular benchmark is a little less than 3 times faster than 2.6 > 3) Shared buffers 3000 > > pgbench -c5 -t100 test > tps = 132.489569 (including connections establishing) > tps = 135.177003 (excluding connections establishing) > > pgbench -c5 -t1000 test > tps = 70.272855 (including connections establishing) > tps = 70.343452 (excluding connections establishing) > > pgbench -c10 -t100 test > tps = 121.624524 (including connections establishing) > tps = 123.549086 (excluding connections establishing) [...] > 4) noatime enabled Shared buffers 3000 > > pgbench -c5 -t100 test > tps = 90.850600 (including connections establishing) > tps = 92.053686 (excluding connections establishing) > > pgbench -c5 -t1000 test > tps = 92.209724 (including connections establishing) > tps = 92.329682 (excluding connections establishing) > > pgbench -c10 -t100 test > tps = 79.264231 (including connections establishing) > tps = 80.145448 (excluding connections establishing) I'm a little skeptical of the consistency of these numbers (several people have observed in the past that it's difficult to get pgbench to produce reliable results) -- how is it possible that using noatime can possibly *reduce* performance by 50%, in the case of the first and third benchmarks? -Neil