Search Postgresql Archives

Re: Monitoring number of backends

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

 



* John R Pierce (pierce@xxxxxxxxxxxx) wrote:
> On 10/22/2013 10:59 AM, Stephen Frost wrote:
> >PG is really*much*  happier if you have only one backend per CPU in your
> >system.  The way to get there is by using a connection pooler like
> >pg_bouncer and configuring it based on how many CPUs you have.
> 
> Actually, I've found peak throughputs on a decent multicore server
> with lots of ram, and lots of disk IO parallelism (eg, big raid10)
> is aruond 2X the socket*hyperthread*core count... so for instance,
> on a modern 2 socket E5-2665 kind of server, thats 2 x 8 cores with
> 2 threads per core, thats 16 total cores, 32 total hardware threads,
> so about 64 database connections would be peak, given a decent
> raid10 of lots of SAS2 10k/15k disks

Sure.  As always with performance- test, test, test on gear that is as
close to identical to the prod gear (or the prod gear itself, if you can
get away with it) as possible..  Every workload is different.

	Thanks,

		Stephen

Attachment: signature.asc
Description: Digital signature


[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