From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
---|---|
To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 8.3devel slower than 8.2 under read-only load |
Date: | 2007-11-24 22:30:03 |
Message-ID: | 1d4e0c10711241430p1357d70cq873773cf792c6376@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Nov 24, 2007 5:16 PM, Gregory Stark <stark(at)enterprisedb(dot)com> wrote:
> Several of the major changes in 8.3 are I/O vs CPU tradeoffs which could be
> causing a slowdown if you're measuring primarily CPU resources. I'm thinking
> of both HOT and packed varlenas. I don't know if either of these are causing
> your slowdown but it's possible.
Here are some rough results:
http://people.openwide.fr/~gsmet/postgresql/postgresql_8.3_development_cycle_1.png
I don't pretend that this bench is realistic but it's a first step. I
run the tests with weird numbers more than 3 times to check that they
are consistent.
IIRC, packed varlenas were commited during April and HOT at the end of
September.
--
Guillaume
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-24 22:30:42 | Re: Open 8.3 issues |
Previous Message | Greg Smith | 2007-11-24 22:06:35 | Re: Open 8.3 issues |