| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Vlad <marchenko(at)gmail(dot)com> |
| Cc: | 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-16 20:31:34 |
| Message-ID: | CAHyXU0yus50=7Bz81Dm7syuU1qohfTVcv=2fxZDBXj7M3UT-jw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Nov 16, 2012 at 2:13 PM, Vlad <marchenko(at)gmail(dot)com> wrote:
> ok, I've applied that patch and ran. The stall started around 13:50:45...50
> and lasted until the end
>
> https://dl.dropbox.com/u/109778/postgresql-2012-11-16_134904-stripped.log
>
> the actual log has more data (including statement following each 'spin
> delay' record), but there is some sensitive info inside which I can't share
> with public.
first thoughts:
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?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steven Schlansker | 2012-11-16 20:44:51 | Re: Noticed something odd with pgbench |
| Previous Message | Vlad | 2012-11-16 20:13:33 | Re: High SYS CPU - need advise |