| From: | Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Checkpoint Tuning Question |
| Date: | 2009-07-10 19:25:47 |
| Message-ID: | 82f04dc40907101225v4e3f12b7u4533da8a7ac2ecec@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Hm, I'm not sure I believe any of that except the last bit, seeing that
> he's got plenty of excess CPU capability. But the last bit fits with
> the wimpy-I/O problem, and it also offers something we could test.
> Dan, please see what happens when you vary the wal_buffers setting.
> (Note you need a postmaster restart to change that.)
>
> regards, tom lane
>
Ok, I tried a few different values - 32kb, 64kb, 512kb, 2MB and 10MB.
I'm not seeing any highly noticeable change in behaviour with any
setting - it wasn't a scientific test, but I seem to have about the
same size hiccup with each setting. The hiccup may be slightly
shorter with the 10MB setting, but barely, if it is.
Thanks,
Dan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James B. Byrne | 2009-07-10 19:45:35 | Re: How to trace client sql requests? |
| Previous Message | hubert depesz lubaczewski | 2009-07-10 18:58:35 | Re: How to trace client sql requests? |