| From: | Vlad Marchenko <marchenko(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(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-20 01:23:24 |
| Message-ID: | 50AADB8C.10607@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
OK, so far I settled on excluding connection caching on app side
(Apache::DBI and prepare_cached) from equation and adding pgbouncer as a
counter-measure. This seems to stabilize the situation - at least I'm
not able to push server into high-sys-cpu stall the way how I used to do.
I'm still interested in getting to the bottom of the issue vs
alleviating it with connection poller, so I might setup a server on
Centos 6.3 (kernel ver 2.6.32) and give it a try.
Alternatively, if anyone have ideas on playing with sysctl parameters
related to scheduler - please let me know.
-- vlad
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2012-11-20 01:23:54 | Re: Prepared Statement Name Truncation |
| Previous Message | JulAkmad, Julpikar | 2012-11-20 00:51:13 | Re: [SOLVED] WINDOWS : PostgreSQL 8.4 Server Start Error |