Re: [Proxool-developer] Connection release latency when using proxool with PostgreSQL

[Jean-Henry B. <ber...@ne...>]

bi...@lo... wrote:

>Hi Jean,
>
>On Wed, 2003-12-10 at 11:52, Jean-Henry Berevoescu wrote:
>
>  
>
>>There is a problem in this new setup: the unused connections are released
>>at a slower pace
>>    
>>
>
>Can you clarify what you mean by "released"? The life cycle is that a
>connection is built, [served, returned,]* destroyed. Which bit is taking
>a long time?
>  
>
It is al acting in a weird way. What I do is build-use-returnToPool but 
what I see
is a lot of connections being created and a lot of them lingering in 
TIME_WAIT
state. It is not very clear why.

>>The real problem is that I am expecting to reuse connections a lot 
>>    
>>
>
>By "reuse" do you mean serve the same connection lots of times? Serving
>(and returning) a connection should be very quick.
>  
>
Yes - the pattern of use is as I said before: create-use-returnToPool

>Have you tried switching trace on? That will give you the performance of
>your database calls. Could it be that the database is performing slowly
>and that is what is causing many connections to be built?
>
I switched the tracing on for a short test, but I will do it again and 
will take a
closer look.

Thanks,
Jean

>
>Regards,
>Bill Horsman
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: SF.net Giveback Program.
>Does SourceForge.net help you be more productive?  Does it
>help you create better code?  SHARE THE LOVE, and help us help
>YOU!  Click Here: http://sourceforge.net/donate/
>_______________________________________________
>Proxool-developer mailing list
>Pro...@li...
>https://lists.sourceforge.net/lists/listinfo/proxool-developer
>  
>