| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | sthomas(at)optionshouse(dot)com |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Vlad <marchenko(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: High SYS CPU - need advise |
| Date: | 2012-11-20 22:35:46 |
| Message-ID: | CAMkU=1xzTDgaswki6Ymp=8KXhhzcj7y1vk4OPew3bhALdieQNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Nov 20, 2012 at 2:26 PM, Shaun Thomas <sthomas(at)optionshouse(dot)com> wrote:
> On 11/20/2012 04:08 PM, Jeff Janes wrote:
>
>> Shaun Thomas reports one that is (I assume) not read intensive, but
>> his diagnosis is that this is a kernel bug where a larger
>> shared_buffers for no good reason causes the kernel to kill off its
>> page cache.
>
>
> We're actually very read intensive.
Sorry, that is what I meant. I wrote "not write intensive", then
decided it would be clearer to change "not write" to "read" and then
forgot to remove the "not". I hate it when that happens.
Atomic update commit failure in the meatware :)
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaun Thomas | 2012-11-20 22:41:21 | Re: High SYS CPU - need advise |
| Previous Message | Shaun Thomas | 2012-11-20 22:26:49 | Re: High SYS CPU - need advise |