| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Vlad <marchenko(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(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 15:02:23 |
| Message-ID: | 50AB9B7F.1010306@optionshouse.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/16/2012 02:31 PM, Merlin Moncure wrote:
> no single thing really stands out -- contention is all over the place.
> lwlock, pinbuffer, dynahash (especially). I am again suspicious of
> bad scheduler interaction. any chance we can fire up pgbouncer?
Just want to throw it out there, but we've been having really bad luck
with the scheduler recently. But only when we use 8GB (on our 72GB
system) for shared_buffers. Cut that down to 4GB, and everything is fine
and dandy.
I think the kernel devs have added in some overzealous scheduler code on us.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-11-20 16:03:18 | Re: High SYS CPU - need advise |
| Previous Message | r d | 2012-11-20 14:51:21 | Request for help setting up source tree |