On Mon, Aug 18, 2008 at 9:59 PM, Kim Robinson <Kim.Robinson@hydro.com.au> wrote:
> Great thanks all.
> Can you give me any indication of the performance implications of
> setting pooling=false?
>
Yeap. All the time you would need to connect to postgresql you will
have the overhead of tcp connection establishment as well as the
overhead of postgresql authentication.
I don't know how much this is in time, but you can give it a try with
some tests which opens a connection, do a simple query like select
version() and close it.
I think you could see something like 2 or 3 times slower than with the
pool enabled.
--
Regards,
Francisco Figueiredo Jr.
http://fxjr.blogspot.com
http://www.npgsql.org
