Re: prepared statement functioning range - Mailing list pgsql-general

From Stephen Frost
Subject Re: prepared statement functioning range
Date
Msg-id 20130617021900.GD23363@tamriel.snowman.net
Whole thread Raw
In response to Re: prepared statement functioning range  (高健 <luckyjackgao@gmail.com>)
List pgsql-general
* 高健 (luckyjackgao@gmail.com) wrote:
> Is there any common calculation methods for deciding the max_connections
> value?

max_connections is a hard limit and so you'd want to have that higher
than the number of connections you actually expect to have.  The general
recommendation is to have the same number of connections as you have
CPUs.  If your system ends up being i/o bound, adding more requestors to
the queue waiting for I/O isn't likely to really help, unless you have
multiple I/O zones (eg; using tablespaces or similar).  At that point,
it really gets to be pretty specific to your environment.

Note also that for batch reporting type of work can often be done using
a hot-standby slave, rather than the master, eliminating that I/O load
from the master system.

    Thanks,

        Stephen

Attachment

pgsql-general by date:

Previous
From: 高健
Date:
Subject: Re: prepared statement functioning range
Next
From: 高健
Date:
Subject: JDBC prepared statement is not treated as prepared statement