From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Dave Youatt <dave(at)meteorsolutions(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: hyperthreaded cpu still an issue in 8.4? |
Date: | 2009-07-29 06:22:07 |
Message-ID: | 4A6FEA8F.5040702@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Greg Smith wrote:
> On Wed, 29 Jul 2009, Stefan Kaltenbrunner wrote:
>
>> Well the real problem is that pgbench itself does not scale too well
>> to lots of concurrent connections and/or to high transaction rates so
>> it seriously skews the result.
>
> Sure, but that's what the multi-threaded pgbench code aims to fix, which
> didn't show up until after you ran your tests. I got the 90K select TPS
> with a completely unoptimized postgresql.conf, so that's by no means the
> best it's possible to get out of the new pgbench code on this hardware.
> I've seen as much as a 40% improvement over the standard pgbench code in
> my limited testing so far, and the patch author has seen a 450% one.
> You might be able to see at least the same results you got from sysbench
> out of it.
oh - the 90k tps are with the new multithreaded pgbench? missed that
fact. As you can see from my results I managed to get 83k with the 8.4
pgbench on a slightly slower Nehalem which does not sound too impressive
for the new code...
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-07-29 06:35:22 | Re: hyperthreaded cpu still an issue in 8.4? |
Previous Message | Greg Smith | 2009-07-29 06:04:17 | Re: hyperthreaded cpu still an issue in 8.4? |