From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Benjamin Krajmalnik" <kraj(at)illumen(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Max connections |
Date: | 2009-08-11 13:53:47 |
Message-ID: | 8370.1249998827@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Benjamin Krajmalnik" <kraj(at)illumen(dot)com> writes:
> I am setting up a test environment to simulate a very high load. We
> have a server farm which is receiving data (cold be thousands of
> simultaneous users posting data). I currently have max_connections set
> to 500 and the server is starting ok. If I try to increase the
> max_connections to 1000, the server is unable to start. I am running a
> VM with 4GB RAM. Swap space is not being used, and the system is
> showing about 1.5GB of ram not being utilized.
Quite honestly, you're living in fantasy land if you expect to support
1000 concurrently active backends on such a restricted server. Get
yourself a connection pooler and knock down max_connections to 100 or
so.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Kempter | 2009-08-11 15:05:28 | replay WAL segments without a "base backup" ? |
Previous Message | Anantha V Padmanaban | 2009-08-11 07:48:20 | Space usage |