Re: FWD: fastlock+lazyvzid patch performance - Mailing list pgsql-hackers

From Robert Haas
Subject Re: FWD: fastlock+lazyvzid patch performance
Date
Msg-id BANLkTin=uQNrW3JXoAKnpwsRd9kufKpTvg@mail.gmail.com
Whole thread Raw
In response to FWD: fastlock+lazyvzid patch performance  (karavelov@mail.bg)
List pgsql-hackers
On Fri, Jun 24, 2011 at 3:31 PM,  <karavelov@mail.bg> wrote:
> clients beta2 +fastlock +lazyvzid local socket
> 8 76064 92430 92198 106734
> 16 64254 90788 90698 105097
> 32 56629 88189 88269 101202
> 64 51124 84354 84639 96362
> 128 45455 79361 79724 90625
> 256 40370 71904 72737 82434

I'm having trouble interpreting this table.

Column 1: # of clients
Column 2: TPS using 9.1beta2 unpatched
Column 3: TPS using 9.1beta2 + fastlock patch
Column 4: TPS using 9.1beta2 + fastlock patch + vxid patch
Column 5: ???

At any rate, that is a big improvement on a system with only 8 cores.
I would have thought you would have needed ~16 cores to get that much
speedup.  I wonder if the -M prepared makes a difference ... I wasn't
using that option.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Steve Singer
Date:
Subject: Re: libpq SSL with non-blocking sockets
Next
From: Simon Riggs
Date:
Subject: Re: ALTER TABLE lock strength reduction patch is unsafe