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

From Simon Riggs
Subject Re: Why do we still have commit_delay and commit_siblings?
Date
Msg-id CA+U5nM+xOjGKtiBKMNDpjw6XhhbX1ALUavV2nPX18wWKH4r82Q@mail.gmail.com
Whole thread Raw
In response to Re: Why do we still have commit_delay and commit_siblings?  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On 14 May 2012 07:30, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:

> That said, I wouldn't mind removing commit_delay and commit_siblings.
> They're pretty much impossible to tune correctly, assuming they work as
> advertised. Some hard data would be nice, though, as Robert suggested.

Those parameters were already hard to get any benefit from, even in a
benchmark. In a wide range of cases/settings they produce clear
degradation.

Any thorough testing would involve a range of different hardware
types, so its unlikely to ever occur. So lets just move on.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Why do we still have commit_delay and commit_siblings?
Next
From: Magnus Hagander
Date:
Subject: Re: Why do we still have commit_delay and commit_siblings?