Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 985E26341C5 for ; Mon, 11 Jan 2010 14:25:07 -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 17909-02-5 for ; Mon, 11 Jan 2010 18:24:57 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by mail.postgresql.org (Postfix) with ESMTP id 704BC634BDC for ; Mon, 11 Jan 2010 13:47:11 -0400 (AST) Received: by pwi15 with SMTP id 15so1675037pwi.3 for ; Mon, 11 Jan 2010 09:47:10 -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; bh=36hPFKpVv4HyjDP8q3zfdwofNYGGACFimlsJGUVrNeE=; b=TBIgoAo20wqn0itGsyYdGPJk6oc82+BhUX3ECGITRpIeMw1+GCQiaiJu6W2+cOGohS p7VUkGEKcTQznGSU5gQQDY1tziTfT9CGI3WM6+EhzgQAVs2E21vveEutRk9+hbrSJl0T R1lgx8IlCBpaYj244vrp3sQnwPJgahRLTpaYY= 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; b=GH4lbcrbTRiXu83eEwcfbp7QCCZae+38xkqOlZ/f9L01ekmbTAG8tWLqO5PhaZhUSM ChyrN4lbixfFOHW20FFsTf2mPhTyjYJAyvro8LNa3DT0GAjIxHH8+hocIoaKVZcWOsCG a3T78LTEWhJw0IZftQkkMQSvQ19HYLybzkOM0= MIME-Version: 1.0 Received: by 10.141.214.1 with SMTP id r1mr6755711rvq.251.1263232030225; Mon, 11 Jan 2010 09:47:10 -0800 (PST) In-Reply-To: References: <61039b861001110544o2c352763q13dcf9d78a156714@mail.gmail.com> <61039b861001110842g15bb1f26jc50b6e6762e01427@mail.gmail.com> Date: Mon, 11 Jan 2010 10:47:10 -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 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/198 X-Sequence-Number: 37078 We may want to start looking at query plans for the slowest queries. Use explain analyze to find them and attach them here. I kinda have a feeling you're running into a limit on the speed of your memory though, and there's no real cure for that. You can buy a little time with some query or db tuning, but 250 or more concurrent users is a LOT.