X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 52B53D1B8A9 for ; Tue, 26 Aug 2003 14:44:53 -0300 (ADT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 75314-09 for ; Tue, 26 Aug 2003 14:44:23 -0300 (ADT) Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by svr1.postgresql.org (Postfix) with ESMTP id 1F149D1B8AB for ; Tue, 26 Aug 2003 14:44:22 -0300 (ADT) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-31.mail.demon.net with esmtp (Exim 3.35 #1) id 19rhrh-0000E1-0V; Tue, 26 Aug 2003 18:44:22 +0100 Received: from localhost (localhost.localdomain [127.0.0.1]) by mainbox.archonet.com (Postfix) with ESMTP id 99F291595F; Tue, 26 Aug 2003 18:44:20 +0100 (BST) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id E602F15955; Tue, 26 Aug 2003 18:44:19 +0100 (BST) From: Richard Huxton To: jerome@gmanmi.tv, PgSQL Performance ML Subject: Re: Best tweak for fast results.. ? Date: Tue, 26 Aug 2003 18:44:19 +0100 User-Agent: KMail/1.5 References: <200308262142.52521.jerome@gmanmi.tv> In-Reply-To: <200308262142.52521.jerome@gmanmi.tv> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200308261844.19268.dev@archonet.com> X-Virus-Scanned: by AMaViS snapshot-20020531 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/337 X-Sequence-Number: 3153 On Tuesday 26 August 2003 14:42, JM wrote: > need input on parameter values on confs... > > our database is getting 1000 transactions/sec on peak periods.. > > sitting on RH 7.3 > 2.4.7-10smp > RAM: 1028400 > SWAP: 2040244 > > queries are just simple select statements based on timestamps, varchars... > less on joins... on a 300K rows.. Assuming you're getting good query plans (check the output of EXPLAIN ANALYSE)... Start by checking the output of vmstat/iostat during busy periods - this will tell you whether CPU/IO/RAM is the bottleneck. There is a good starter for tuning PG at: http://www.varlena.com/varlena/GeneralBits/Tidbits/index.php Assuming your rows aren't too wide, they're probably mostly cached by Linux, so you probably don't want to overdo the shared buffers/sort memory and make sure the effective cache size is accurate. -- Richard Huxton Archonet Ltd