From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Cc: | Fei Liu <fei(dot)liu(at)aepnetworks(dot)com> |
Subject: | Re: large number of connected connections to postgres database (v8.0) |
Date: | 2007-07-20 23:28:27 |
Message-ID: | 200707201628.28266.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Fei Liu,
> It appears my multi-thread application (100 connections every 5 seconds)
> is stalled when working with postgresql database server. I have limited
> number of connections in my connection pool to postgresql to 20. At the
> begining, connection is allocated and released from connection pool as
> postgres serves data request. The pool can recover from exhaustion. But
> very quickly (after about 400 client requests), it seems postgres server
> stops serving and connection to postgres server is not released any more
> resulting a resource exhausting for clients.
This sounds more like a problem with your connection pool. Unless
PostgreSQL is slowing down due to CPU/RAM/I/O saturation?
In any case, I doubt the problem is too many connections, or you'd just get
an error message ...
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin M. Roy | 2007-07-21 00:18:53 | Re: Postgres configuration for 64 CPUs, 128 GB RAM... |
Previous Message | Josh Berkus | 2007-07-20 23:26:07 | Re: Postgres configuration for 64 CPUs, 128 GB RAM... |