From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: CLOG contention |
Date: | 2011-12-27 10:23:34 |
Message-ID: | CA+U5nMJN9-GAgHghXwb5=0xtPbwrdpQ3SiOC_dqMhe=b_ON0=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Dec 24, 2011 at 9:25 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Thu, Dec 22, 2011 at 4:20 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Also, if it is that, what do we do about it? I don't think any of the
>> ideas proposed so far are going to help much.
>
> If you don't like guessing, don't guess, don't think. Just measure.
>
> Does increasing the number of buffers solve the problems you see? That
> must be the first port of call - is that enough, or not? If not, we
> can discuss the various ideas, write patches and measure them.
Just in case you want a theoretical prediction to test:
increasing NUM_CLOG_BUFFERS should reduce the frequency of the spikes
you measured earlier. That should happen proportionally, so as that is
increased they will become even less frequent. But the size of the
buffer will not decrease the impact of each event when it happens.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Björnhagen | 2011-12-27 11:39:22 | Re: Standalone synchronous master |
Previous Message | Tom Lane | 2011-12-27 01:18:03 | Re: contrib/README |