| From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
|---|---|
| To: | Anne Rosset <arosset(at)collab(dot)net> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Deterioration in performance when query executed in multi threads |
| Date: | 2013-05-01 16:26:50 |
| Message-ID: | 20130501162650.GI27807@aart.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2013-05-01 17:07:43 | Re: Deterioration in performance when query executed in multi threads |
| Previous Message | Anne Rosset | 2013-05-01 16:07:55 | Re: Deterioration in performance when query executed in multi threads |