Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 093916356EB for ; Wed, 13 Jan 2010 16:44:03 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 36998-03-4 for ; Wed, 13 Jan 2010 20:43:48 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f213.google.com (mail-ew0-f213.google.com [209.85.219.213]) by mail.postgresql.org (Postfix) with ESMTP id A504F64054E for ; Wed, 13 Jan 2010 16:43:33 -0400 (AST) Received: by ewy5 with SMTP id 5so14007515ewy.34 for ; Wed, 13 Jan 2010 12:43:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=CEytUFdkPZdYtjSnvXBzlyd1CqQsrtOs33EmgcMgbYo=; b=GcRXjZfHAK8jUC7tuUojp1lISpIRH7d71K2Mwd1vXuBR4zRME0S6rCcVywwAejqyDo f1RvJOWFbulVvZBKnrS7BBbEJ/d+/r1wfT3hyghRqhPWPuMgrbIEE5OmdmmBc25kagfl a2AP31EyErzR5lFnHQM8+ciFIkNdlmNmtTIGw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=VbnyCBv49bQid/x+VHHsBMt4EB9HRv2h5mJ13nSR3svqntE42Q/Uup2lvfibyxBIKR xEe+LDFqdEQOwky+ld6Jq/fh3CSwIauQNF+mMYvYDmXhZc5Q689IHEpKwKgd9CzYpHYl 1vq56WFwf+s0tJotPn3muq99lU7WZxpLPiqnw= MIME-Version: 1.0 Received: by 10.216.87.143 with SMTP id y15mr3247507wee.39.1263415409981; Wed, 13 Jan 2010 12:43:29 -0800 (PST) In-Reply-To: <61039b861001131210j673f1200r16f60f26f5a22265@mail.gmail.com> References: <4B4B177B020000250002E194@gw.wicourts.gov> <4B4B3BF6020000250002E1B1@gw.wicourts.gov> <61039b861001111323g531a5d68q1f59171d926aefef@mail.gmail.com> <61039b861001121001p37dc7698i48651189edcee9d0@mail.gmail.com> <4B4D53BF.4020905@postnewspapers.com.au> <61039b861001131210j673f1200r16f60f26f5a22265@mail.gmail.com> Date: Wed, 13 Jan 2010 13:43:29 -0700 Message-ID: Subject: Re: performance config help From: Scott Marlowe To: Bob Dusek Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.589 tagged_above=-10 required=5 tests=BAYES_00=-2.599, FH_DATE_PAST_20XX=3.188 X-Spam-Level: X-Archive-Number: 201001/264 X-Sequence-Number: 37144 On Wed, Jan 13, 2010 at 1:10 PM, Bob Dusek wrote: > And, we pretty much doubled our capacity... from approx 40 "requests" > per second to approx 80. Excellent! > The problem with our "cheap" connection pool is that the persistent > connections don't seem to be available immediately after they're > released by the previous process. =A0 pg_close doesn't seem to help the > situation. =A0We understand that pg_close doesn't really close a > persistent connection, but we were hoping that it would cleanly > release it for another client to use. =A0Curious. Yeah, the persistent connects in php are kinda as dangerous as they are useful.. Have you tried using regular connects just to compare performance? On Linux they're not too bad, but on Windows (the pg server that is) it's pretty horrible performance-wise. > We've also tried third-party connection pools and they don't seem to > be real fast. What have you tried? Would pgbouncer work for you?