X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C34733A48A7 for ; Thu, 4 Nov 2004 16:33:49 +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 24825-08 for ; Thu, 4 Nov 2004 16:33:48 +0000 (GMT) Received: from neptune.lgu.ac.uk (neptune.lgu.ac.uk [140.97.30.6]) by svr1.postgresql.org (Postfix) with ESMTP id E30053A48CF for ; Thu, 4 Nov 2004 16:33:46 +0000 (GMT) Received: from solent (cal42-234.lgu.ac.uk [140.97.42.234]) by neptune.lgu.ac.uk (8.12.10/8.12.10) with ESMTP id iA4GXKO6022007; Thu, 4 Nov 2004 16:33:21 GMT Reply-To: From: "Matt Clark" To: "'Martin Foster'" , "'Kevin Barnard'" Cc: "'PostgreSQL Performance'" Subject: Re: Restricting Postgres Date: Thu, 4 Nov 2004 16:33:33 -0000 Organization: Ymogen Ltd Message-ID: <002e01c4c28c$06e83df0$8300a8c0@solent> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <418A5590.5090006@ethereal-realms.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal X-LGU-MailScanner: Found to be clean X-MailScanner-From: matt@ymogen.net X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/47 X-Sequence-Number: 9001 > Apache::DBI overall works better to what I require, even if > it is not a > pool per sey. Now if pgpool supported variable rate pooling like > Apache does with it's children, it might help to even things > out. That > and you'd still get the spike if you have to start the webserver and > database server at or around the same time. I still don't quite get it though - you shouldn't be getting more than one child per second being launched by Apache, so that's only one PG postmaster per second, which is really a trivial load. That is unless you have 'StartServers' set high, in which case the 'obvious' answer is to lower it. Are you launching multiple DB connections per Apache process as well?