Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 0C8C7659E18 for ; Wed, 13 Jan 2010 16:33:35 -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 35230-01-2 for ; Wed, 13 Jan 2010 20:33:24 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mail.postgresql.org (Postfix) with ESMTP id AC4BE65A190 for ; Wed, 13 Jan 2010 16:10:07 -0400 (AST) Received: by ey-out-2122.google.com with SMTP id 22so4131476eye.33 for ; Wed, 13 Jan 2010 12:10:06 -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:content-type; bh=8U+iq99cAUkS9vdDj+Wv8I5LLBfU9o9FZmWBjOuIgYg=; b=Rks7njJH8DRKSDPXSb+52ArqIN0q0LLOwTprHTuBobFGFdjNsqzRqSG8V7+T248i72 2p3GSMU41Ed3i3VnLNDmaSmJR7Ste9H9xfu1LUvaEAUZKoDz4JY2aePp9VIulvJqc4V6 f3zkes6LEL/Mc5ffLAMQ82Q4IV1Go6TerCAMY= 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 :content-type; b=hlCDPnh60PQNEpPmq6XDY+xsIGsxwUHA+pEsc3eyHIvWOyn3cb6w1Whl8RUzZ8PrdC 5/PdH5k+dEQFJ/jcztGYCp74KftzRw97pi/Jb2fmul7TDMwAGP8lGmdxjEN1qEvbg7ZF Ylu0zkR6n+wJ+uo5qEPuEwtbZ66stDzl2HsDY= MIME-Version: 1.0 Received: by 10.216.90.79 with SMTP id d57mr787836wef.117.1263413405063; Wed, 13 Jan 2010 12:10:05 -0800 (PST) In-Reply-To: <4B4D53BF.4020905@postnewspapers.com.au> References: <4B4B177B020000250002E194@gw.wicourts.gov> <4B4B3BF6020000250002E1B1@gw.wicourts.gov> <61039b861001111323g531a5d68q1f59171d926aefef@mail.gmail.com> <61039b861001121001p37dc7698i48651189edcee9d0@mail.gmail.com> <4B4D53BF.4020905@postnewspapers.com.au> Date: Wed, 13 Jan 2010 15:10:04 -0500 Message-ID: <61039b861001131210j673f1200r16f60f26f5a22265@mail.gmail.com> Subject: Re: performance config help From: Bob Dusek To: pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 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/263 X-Sequence-Number: 37143 FYI - We have implemented a number of changes... a) some query and application optimizations b) connection pool (on the cheap: set max number of clients on Postgres server and created a blocking wrapper to pg_pconnect that will block until it gets a connection) c) moved the application server to a separate box And, we pretty much doubled our capacity... from approx 40 "requests" per second to approx 80. 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. pg_close doesn't seem to help the situation. We 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. Curious. We've also tried third-party connection pools and they don't seem to be real fast. Thanks for all of your input. We really appreciate it. Bob