| 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>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: High SYS CPU - need advise |
| Date: | 2012-11-21 17:09:32 |
| Message-ID: | CAHyXU0xxEd+N26pc+vYiV5sTk_56bF=m3xfLOF+KsJA4su2f-A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Nov 21, 2012 at 11:05 AM, Vlad <marchenko(at)gmail(dot)com> wrote:
> it's session mode and the pool size is 1200 (cause I need to grantee that in
> the worst case we have enough slots for all possible clients), however even
> at the times preceding high-cpu-sys-stall, the number postmasters are like
> 15-20. When stall happens, it starts to raise but that's the result of DB
> not answering in timely manner.
That is completely defeating the point. Mode should be transaction
mode and somewhere between 1-2x the number of cores for the pool size.
Note the # of connected clients does not have to equal the size of
the pool -- that's the whole point of pgboucner -- it forces the
queries through a fixed number of backend processes.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2012-11-21 17:18:46 | Re: High SYS CPU - need advise |
| Previous Message | Vlad | 2012-11-21 17:05:05 | Re: High SYS CPU - need advise |