X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 54659D1B181 for ; Thu, 13 May 2004 10:57:16 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 06332-04 for ; Thu, 13 May 2004 10:56:59 -0300 (ADT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id 07CB3D1B178 for ; Thu, 13 May 2004 10:56:55 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 1A20F34450; Thu, 13 May 2004 10:57:01 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 18F83342AA for ; Thu, 13 May 2004 10:57:01 -0300 (ADT) X-Received: from localhost ([unix socket]) by ganymede.hub.org (Cyrus v2.2.3) with LMTP; Thu, 13 May 2004 04:30:42 -0300 X-Sieve: CMU Sieve 2.2 X-Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id DB7F335A95 for ; Thu, 13 May 2004 04:30:33 -0300 (ADT) X-Received: from mail.postgresql.org [200.46.204.71] by localhost with IMAP (fetchmail-6.2.5) for scrappy@localhost (single-drop); Thu, 13 May 2004 04:30:33 -0300 (ADT) X-Received: from svr1.postgresql.org ([unix socket]) by svr1.postgresql.org (Cyrus v2.2.3) with LMTP; Thu, 13 May 2004 04:29:49 -0300 X-Sieve: CMU Sieve 2.2 X-Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D5124D1C9C4 for ; Thu, 13 May 2004 04:29:49 -0300 (ADT) X-Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 19662-01 for ; Thu, 13 May 2004 04:29:30 -0300 (ADT) X-Received: from linda-2.paradise.net.nz (bm-2a.paradise.net.nz [202.0.58.21]) by svr1.postgresql.org (Postfix) with ESMTP id 46909D1E741 for ; Thu, 13 May 2004 04:29:28 -0300 (ADT) X-Received: from smtp-3.paradise.net.nz (smtp-3b.paradise.net.nz [202.0.32.212]) by linda-2.paradise.net.nz (Paradise.net.nz) with ESMTP id <0HXN00EUM65364@linda-2.paradise.net.nz> for psql-performance@postgresql.org; Thu, 13 May 2004 19:29:28 +1200 (NZST) X-Received: from paradise.net.nz (203-79-100-194.adsl.paradise.net.nz [203.79.100.194]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id A386DADF83; Thu, 13 May 2004 19:29:27 +1200 (NZST) Date: Thu, 13 May 2004 19:31:29 +1200 From: Mark Kirkwood Subject: Re: Clarification on some settings In-reply-to: <40A1E83E.2000402@frodo.hserus.net> To: Shridhar Daithankar Cc: Doug Y , psql-performance@postgresql.org Message-id: <40A32451.4010801@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040404 References: <6.0.1.1.2.20040511163104.01e9cbb0@mail.traderonline.com> <40A1E83E.2000402@frodo.hserus.net> X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-DCC: : X-Spam-Pyzor: ReSent-Date: Thu, 13 May 2004 10:56:55 -0300 (ADT) Resent-From: "Marc G. Fournier" Resent-To: pgsql-performance@postgresql.org ReSent-Subject: Re: [PERFORM] Clarification on some settings ReSent-Message-ID: <20040513105655.G58152@ganymede.hub.org> X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/123 X-Sequence-Number: 6954 Note that effective_cache_size is merely a hint to that planner to say "I have this much os buffer cache to use" - it is not actually allocated. It is shared_buffers that will hurt you if it is too high (10000 - 25000 is the usual sweet spot). best wishes Mark Shridhar Daithankar wrote: > >> >> Increasing the effective cache and sort mem didn't seem to make much >> of a difference. I'm guessing the eff cache was probably raised a bit >> too much, and shared_buffers is way to high. > > > I agree. For shared buffers start with 5000 and increase in batches on > 1000. Or set it to a high value and check with ipcs for maximum shared > memory usage. If share memory usage peaks at 100MB, you don't need > more than say 120MB of buffers. > > >