From: Neil Conway <neilc@samurai.com>
To: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
Cc: pgsql-performance@postgresql.org
Subject: Re: Comparing postgresql7.4 CVS head on linux 2.4.20 and 2.6.0-test4
Date: Wed, 27 Aug 2003 19:00:14 -0400
Message-ID: <20030827230014.GA63737@home.samurai.com> (raw)
In-Reply-To: <200308272102.26319.shridhar_daithankar@persistent.co.in>
References: <200308272102.26319.shridhar_daithankar@persistent.co.in>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: neilc@samurai.com, shridhar_daithankar@persistent.co.in
Subject: Re: Comparing postgresql7.4 CVS head on linux 2.4.20 and 2.6.0-test4
In-Reply-To: <20030827230014.GA63737@home.samurai.com>
References: <200308272102.26319.shridhar_daithankar@persistent.co.in> <20030827230014.GA63737@home.samurai.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox