From: | "Francisco Figueiredo Jr(dot)" <francisco(at)npgsql(dot)org> |
---|---|
To: | "Kim Robinson" <Kim(dot)Robinson(at)hydro(dot)com(dot)au> |
Cc: | "Magnus Hagander" <magnus(at)hagander(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postres.exe Processes Hang |
Date: | 2008-08-19 01:50:22 |
Message-ID: | 438d02260808181850x1c5f766fgbf8b110ab05c46b6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Aug 18, 2008 at 9:59 PM, Kim Robinson <Kim(dot)Robinson(at)hydro(dot)com(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Brent Wood | 2008-08-19 05:36:02 | Re: What's size of your PostgreSQL Database? |
Previous Message | Kim Robinson | 2008-08-19 00:59:13 | Re: Postres.exe Processes Hang |