Re: Why do we still have commit_delay and commit_siblings? - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Why do we still have commit_delay and commit_siblings?
Date
Msg-id CAMkU=1xL3xrP6YgOF9XmTE+D5AnQ0TEckTYdXwOXeOxTjHus9Q@mail.gmail.com
Whole thread Raw
In response to Re: Why do we still have commit_delay and commit_siblings?  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Why do we still have commit_delay and commit_siblings?
List pgsql-hackers
On Sun, May 13, 2012 at 11:07 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>
> Keeping a parameter without any clue as to whether it has benefit is
> just wasting people's time.
>
> We don't ADD parameters based on supposition, why should we avoid
> removing parameters that have no measured benefit?

Using pgbench -T30 -c 2 -j 2 on a 2 core laptop system, with a scale
that fits in shared_buffers:

--commit-delay=2000 --commit-siblings=0
tps = 162.924783 (excluding connections establishing)

--commit-delay=0 --commit-siblings=0
tps = 89.237578 (excluding connections establishing)

Cheers,

Jeff


pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Why do we still have commit_delay and commit_siblings?
Next
From: Robert Haas
Date:
Subject: Re: Why do we still have commit_delay and commit_siblings?