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 5A481D1B4FE for ; Wed, 17 Sep 2003 11:01:21 +0000 (GMT) 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 85749-09 for ; Wed, 17 Sep 2003 08:01:13 -0300 (ADT) Received: from smtp.pspl.co.in (unknown [202.54.11.65]) by svr1.postgresql.org (Postfix) with ESMTP id 93A55D1B4EF for ; Wed, 17 Sep 2003 08:01:08 -0300 (ADT) Received: (from root@localhost) by smtp.pspl.co.in (8.12.9/8.12.9) id h8HBBJmE009476 for ; Wed, 17 Sep 2003 16:41:19 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) (authenticated bits=0) by persistent.co.in (8.12.9/8.12.9) with ESMTP id h8HBBICl009463 for ; Wed, 17 Sep 2003 16:41:18 +0530 From: "Shridhar Daithankar" To: Date: Wed, 17 Sep 2003 16:33:09 +0530 MIME-Version: 1.0 Subject: Re: Effective Cache Size Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3F688CC5.12621.4EBFDCC@localhost> In-reply-to: <8F4A22E017460A458DB7BBAB65CA6AE502AA15@webbased9> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/242 X-Sequence-Number: 3608 On 17 Sep 2003 at 11:48, Nick Barr wrote: > Hi, > > I have been following a thread on this list "Inconsistent performance" > and had a few questions especially the bits about effective_cache_size. > I have read some of the docs, and some other threads on this setting, > and it seems to used by the planner to either choose a sequential or > index scan. So it will not necessarily increase performance I suppose > but instead choose the most optimal plan. Is this correct? That is correct. > Danger maths ahead. Beware!!!! > > > 141816K buff > + 1781764K cached > ----------------- > 1923580K total > > effective_cache_size = 1923580 / 8 = 240447.5 > That would be bit too aggressive. I would say set it around 200K to leave room for odd stuff. Rest seems fine with your configuration. Of course a latest version of postgresql is always good though.. Bye Shridhar -- Power is danger. -- The Centurion, "Balance of Terror", stardate 1709.2