| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
| Cc: | denis(at)edistar(dot)com, Jeff Trout <threshar(at)torgo(dot)978(dot)org>, 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 18:27:44 |
| Message-ID: | 1122488864.15145.114.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2005-07-27 at 12:53, Jim C. Nasby wrote:
> On Wed, Jul 27, 2005 at 04:46:56PM +0200, denis(at)edistar(dot)com wrote:
> > I'm now testing with pg_pool installed on each apache frontend with 260
> > pg_pool preforked clients in each machine.
> >
> > The database seems to work better. At least when it goes to swap it
> > doesn't stop working...
>
> Wait, are you saying your database server is swapping? You'll never get
> any kind of performance if that's the case.
IF it swaps out unused code / data and leaves it, that's fine, but if
it's constantly swapping out then yeah, that's a VERY bad thing.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2005-07-27 18:36:16 | pgsql mention on zdnet |
| Previous Message | Robert Treat | 2005-07-27 17:55:51 | Re: duplicate messages? |