Search Postgresql Archives

Re: High SYS CPU - need advise

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It turned out we can't use transaction mode, cause there are prepared statement used a lot within code, while processing a single http request.

Also, I can't 100% rule out that there won't be any long running (statistical) queries launched (even though such requests should not come to this database), which would occupy connection for longer time, but do not create any race condition... So having pool size at 8 may be too slim .

It's a single database.

-- Vlad


On Wed, Nov 21, 2012 at 12:04 PM, Merlin Moncure <mmoncure@xxxxxxxxx> wrote:
On Wed, Nov 21, 2012 at 11:56 AM, Vlad <marchenko@xxxxxxxxx> wrote:
> ok, understood.
> I need to give some more thoughts to if it's possible for us to switch to
> transaction mode from app standpoint of view.
>
> if yes, then setting pool size to 20 (for 8 cores)  sounds OK?

If it was me, I would be starting with exactly 8 and be tuning from there.

Don't forget: each database role gets its own pool.

merlin


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux