Re: Deterioration in performance when query executed in multi threads - Mailing list pgsql-performance

From ktm@rice.edu
Subject Re: Deterioration in performance when query executed in multi threads
Date
Msg-id 20130501162650.GI27807@aart.rice.edu
Whole thread Raw
In response to Re: Deterioration in performance when query executed in multi threads  (Anne Rosset <arosset@collab.net>)
Responses Re: Deterioration in performance when query executed in multi threads  (Scott Marlowe <scott.marlowe@gmail.com>)
Re: Deterioration in performance when query executed in multi threads  (Anne Rosset <arosset@collab.net>)
List pgsql-performance
On Wed, May 01, 2013 at 04:07:55PM +0000, Anne Rosset wrote:
> Hi Ken,
> Thanks for your answer. My test is actually running with jboss 7/jdbc and the connection pool is defined  with
min-pool-size=10 and max-pool-size=400. 
>
> Why would you think it is an issue with the connection pool?
>
> Thanks,
> Anne
>

Hi Anne,

You want to be able to run as many jobs productively at once as your hardware is
capable of supporting. Usually something starting a 2 x number of CPUs is best.
If you make several runs increasing the size of the pool each time, you will
see a maximum throughput somewhere near there and then the performance will
decrease as you add more and more connections. You can then use that sweet spot.
Your test harness should make that pretty easy to find.

Regards,
Ken


pgsql-performance by date:

Previous
From: Anne Rosset
Date:
Subject: Re: Deterioration in performance when query executed in multi threads
Next
From: Scott Marlowe
Date:
Subject: Re: Deterioration in performance when query executed in multi threads