X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 10D573AC283 for ; Thu, 30 Dec 2004 05:30:42 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 05097-06 for ; Thu, 30 Dec 2004 05:30:20 +0000 (GMT) Received: from tetra.ehpg.net (tetra.ehpg.net [216.218.206.34]) by svr1.postgresql.org (Postfix) with ESMTP id 83E9C3AC2AC for ; Thu, 30 Dec 2004 05:30:20 +0000 (GMT) Received: from ppp-68-122-211-163.dsl.irvnca.pacbell.net ([68.122.211.163] helo=gentoo.homenetwork) by tetra.ehpg.net with esmtpa (Exim 4.42) id 1Cjst6-0001RK-Ne; Wed, 29 Dec 2004 21:30:17 -0800 Subject: Re: too many clients From: "Gavin M. Roy" To: Greg Stark Cc: Frank Bax , pgsql-php@postgresql.org In-Reply-To: <87y8fg8iqi.fsf@stark.xeocode.com> References: <330532b604122908387f7ffde2@mail.gmail.com> <0DC9A380-59AB-11D9-B3B3-0003938BDF32@localnotion.com> <330532b604122908387f7ffde2@mail.gmail.com> <5.2.1.1.0.20041229125718.00a02520@pop6.sympatico.ca> <1104363131.32605.30.camel@localhost> <87y8fg8iqi.fsf@stark.xeocode.com> Content-Type: text/plain Organization: 800 Pound Gorilla Date: Wed, 29 Dec 2004 21:33:08 -0800 Message-Id: <1104384788.32609.42.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.038 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200412/8 X-Sequence-Number: 2966 My primary setup that I use this in is an back-end for an application that uses XML over HTTP to talk to a PHP application using PgSQL. It's run in production for a long time, on modest hardware (dual xeon, 4 gigs ram, raid 5 ultra 160 drives - pgsql that is). On Thu, 2004-12-30 at 00:20 -0500, Greg Stark wrote: > "Gavin M. Roy" writes: > > > I use it on a few very high traffic sites without issue, but it is tuned so > > that there is only 1 persistant connection per apache backend and postgresql > > will allow the max apache backends, which by default is generally 256. I > > highly recommend it in such a situation, while I generally do not recommend > > it in any other. > > That doesn't sound reasonable. Does your machine really have so many > processors or i/o bandwidth that 256 postgres processes can really all make > progress? > > Or do you have images and static html on the same web server? If so I suggest > moving them to another web server. No need to have a postgres instance (and a > php instance) sitting idle consuming memory waiting until someone happens to > hit a dynamic page. >