Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 00AA61337BF2 for ; Mon, 4 Apr 2011 07:28:18 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 48820-07 for ; Mon, 4 Apr 2011 10:28:08 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from elizabeth.gransy.com (elizabeth.gransy.com [89.187.132.199]) by mail.postgresql.org (Postfix) with ESMTP id 69C511337BEC for ; Mon, 4 Apr 2011 07:28:07 -0300 (ADT) Received: from sq.gransy.com (localhost [127.0.0.1]) by elizabeth.gransy.com (Postfix) with ESMTP id 2DCEF15E432B; Mon, 4 Apr 2011 12:28:06 +0200 (CEST) Received: from 85.161.195.250 (SquirrelMail authenticated user tv@fuzzy.cz) by sq.gransy.com with HTTP; Mon, 4 Apr 2011 12:28:06 +0200 Message-ID: <8b57d989ff79004f9159326f008abefb.squirrel@sq.gransy.com> In-Reply-To: <4D999211.9080507@orkash.com> References: <4D999211.9080507@orkash.com> Date: Mon, 4 Apr 2011 12:28:06 +0200 Subject: Re: Postgres Performance Tuning From: tv@fuzzy.cz To: "Adarsh Sharma" Cc: pgsql-performance@postgresql.org User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201104/8 X-Sequence-Number: 43070 > max_connections = 700 > shared_buffers = 4096MB > temp_buffers = 16MB > work_mem = 64MB > maintenance_work_mem = 128MB > wal_buffers = 32MB > checkpoint_segments = 32 > random_page_cost = 2.0 > effective_cache_size = 4096MB First of all, there's no reason to increase wal_buffers above 32MB. AFAIK the largest sensible value is 16MB - I doubt increasing it further will improve performance. Second - effective_cache_size is just a hint how much memory is used by the operating system for filesystem cache. So this does not influence amount of allocated memory in any way. > but Still Postgres Server uses Swap Memory While SELECT & INSERT into > database tables. Are you sure it's PostgreSQL. What else is running on the box? Have you analyzed why the SQL queries are slow (using EXPLAIN)? regards Tomas