Re: Fixed xloginsert_locks for 9.4

From: Gregory Smith <gregsmithpgsql(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fixed xloginsert_locks for 9.4
Date: 2014-10-03 14:07:39
Message-ID: 542EADAB.2040805@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/3/14, 8:26 AM, Andres Freund wrote:
> #define NUM_XLOGINSERT_LOCKS 1
> tps = 52.711939 (including connections establishing)
> #define NUM_XLOGINSERT_LOCKS 8
> tps = 286.496054 (including connections establishing)
> #define NUM_XLOGINSERT_LOCKS 16
> tps = 346.113313 (including connections establishing)
> #define NUM_XLOGINSERT_LOCKS 24
> tps = 363.242111 (including connections establishing)

Just to clarify: that 10% number I threw out was meant as a rough
estimate for a system with the default configuration, which is all that
I tested. It seemed like people would likely need to tune all the usual
things like checkpoint_segments, shared_buffers, etc. as well before
seeing much better. You did all that, and sure enough the gain went up;
thanks for confirming my guess.

I still don't think that means this needs a GUC for 9.4. Look at that
jump from 1 to 8. The low-hanging fruit here hasn't just been knocked
off. It's been blended into a frozen drink, poured into a glass, and
had a little paper umbrella put on top. I think that's enough for 9.4.
But, yes, let's see if we can add delivery to the side of the pool in
the next version too.

--
Greg Smith greg(dot)smith(at)crunchydatasolutions(dot)com
Chief PostgreSQL Evangelist - http://crunchydatasolutions.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-10-03 14:11:30 Re: Fixed xloginsert_locks for 9.4
Previous Message Heikki Linnakangas 2014-10-03 13:28:17 Re: WAL format and API changes (9.5)