Re: Deterioration in performance when query executed in multi threads

From: Anne Rosset <arosset(at)collab(dot)net>
To: "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu>
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:07:55
Message-ID: 9A6B86D66BD3C2438AFACFA09354890F20A2E06C@EXCH01.sp.corp.collab.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

-----Original Message-----
From: ktm(at)rice(dot)edu [mailto:ktm(at)rice(dot)edu]
Sent: Wednesday, May 01, 2013 7:13 AM
To: Anne Rosset
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Deterioration in performance when query executed in multi threads

On Wed, May 01, 2013 at 02:05:06PM +0000, Anne Rosset wrote:
> Hi all,
> We are running a stress test that executes one select query with multiple threads.
> The query executes very fast (10ms). It returns 100 rows. I see deterioration in the performance when we have multiple threads executing the query. With 100 threads, the query takes between 3s and 8s.
>
> I suppose there is a way to tune our database. What are the parameters
> I should look into? (shared_buffer?, wal_buffer?)
>
> Thanks for your help,
> Anne

Try a connection pooler like pgbouncer to keep the number of simultaneous queries bounded to a reasonable number. You will actually get better performance.

Regards,
Ken

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message ktm@rice.edu 2013-05-01 16:26:50 Re: Deterioration in performance when query executed in multi threads
Previous Message Stefan de Konink 2013-05-01 15:44:54 Re: [BUGS] BUG #8130: Hashjoin still gives issues