> -Original Message-
> From: pgsql-performance-ow...@postgresql.org [mailto:pgsql-performance-
> ow...@postgresql.org] On Behalf Of Ivan Voras
> Sent: Wednesday, January 26, 2011 6:25 AM
> To: pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] Queries becoming slo
On 25/01/2011 22:37, Anne Rosset wrote:
Hi,
We are running some performances tests. With a lot of concurrent
access, queries get very slow. When there is no load, those queries run
fast.
As others said, you need to stat how many concurrent clients are working
on the database and also the nu
When you say that with a lot of concurrent access, queries get very slow, How
many concurrent connections to your server have you had?
more that max_connections´value?
If you want to have many concurrent connections, you should have consider to
use a pooling connection system like pgbouncer or p
"Anne Rosset" wrote:
> We are running some performances tests. With a lot of concurrent
> access, queries get very slow. When there is no load, those
> queries run fast.
What's "a lot"?
> We kind of see a trend about these queries: it seems like the
> ones that become very slow have an ORD
On 1/25/2011 3:37 PM, Anne Rosset wrote:
Hi,
We are running some performances tests. With a lot of concurrent access,
queries get very slow. When there is no load, those queries run fast.
We kind of see a trend about these queries: it seems like the ones that
become very slow have an ORDER BY o
