Re: Postgresql with max_connections=4096

From: Jeff Trout <threshar(at)torgo(dot)978(dot)org>
To: denis(at)edistar(dot)com
Cc: Richard Huxton <dev(at)archonet(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgresql with max_connections=4096
Date: 2005-07-27 13:04:42
Message-ID: 92EA2D56-2980-4A02-889B-42487BF34DC1@torgo.978.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Jul 27, 2005, at 4:22 AM, denis(at)edistar(dot)com wrote:

> Already checked.
> We set a machine with only pg_pool installed as a fronted to the
> real db.
> If I disable persistent connections and I use pg_pool with 4096
> preforked clients,

no no no.
you don't want 4096 preforked clients.

What you want to do is leave it at the default 32 preforks and run a
copy of pgpool on each frontend. Then point your app to connect ot
localhost (or the unix socket). Be sure you change things to use a
"normal" connect not a persistant connect. This should be fine for
you. I used to run a site doing hundreds of connects & queries /
second across 4 frontends each of which ran a pg_pool connected to a
db box.

If you fine 32 clients isn't enough, then bump it up. The idea is to
keep as few connections as possible.

--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alexey Borzov 2005-07-27 13:07:03 Re: ENUM type
Previous Message Andrew Stewart 2005-07-27 12:56:24 Daily digest?