From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Group Commit |
Date: | 2007-04-10 03:14:25 |
Message-ID: | Pine.GSO.4.64.0704092249360.21736@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 9 Apr 2007, Bruce Momjian wrote:
> The big question is who is going to care about the milliseconds delay
> and is using a configuration that is going to benefit from commit_delay.
I care. WAL writes are a major bottleneck when many clients are
committing near the same time. Both times I've played with the
commit_delay settings I found it improved the peak throughput under load
at an acceptable low cost in latency. I'll try to present some numbers on
that when I get time, before you make me cry by taking it away.
An alternate mechanism that tells the client the commit is done when it
hasn't hit disk is of no use for the applications I work with, so I
haven't even been paying attention to no-commit-wait.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-04-10 03:28:59 | Re: Group Commit |
Previous Message | ITAGAKI Takahiro | 2007-04-10 02:02:00 | Re: [PATCHES] Fix mdsync never-ending loop problem |