Date: Wed, 27 Jul 2005 12:53:29 -0500
From: "Jim C. Nasby" <decibel@decibel.org>
To: denis@edistar.com
Cc: Jeff Trout <threshar@torgo.978.org>, Richard Huxton <dev@archonet.com>,
	"pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Postgresql with max_connections=4096
Message-ID: <20050727175329.GX26758@decibel.org>
References: <42E73347.7010500@edistar.com> <42E73D54.10001@archonet.com>
	<42E74458.70704@edistar.com>
	<92EA2D56-2980-4A02-889B-42487BF34DC1@torgo.978.org>
	<42E79E60.2060104@edistar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42E79E60.2060104@edistar.com>
User-Agent: Mutt/1.5.9i
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

On Wed, Jul 27, 2005 at 04:46:56PM +0200, denis@edistar.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.
-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend