pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: tv@fuzzy.cz
To: Adarsh Sharma <adarsh.sharma@orkash.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres Performance Tuning
Date: Mon, 4 Apr 2011 12:28:06 +0200
Message-ID: <8b57d989ff79004f9159326f008abefb.squirrel@sq.gransy.com> (raw)
In-Reply-To: <4D999211.9080507@orkash.com>
References: <4D999211.9080507@orkash.com>

> 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




view thread (22+ messages)  latest in thread

Message-ID: <8b57d989ff79004f9159326f008abefb.squirrel@sq.gransy.com>
Permalink:  ../8b57d989ff79004f9159326f008abefb.squirrel@sq.gransy.com/
Also on:    postgresql.org/message-id/8b57d989ff79004f9159326f008abefb.squirrel@sq.gransy.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tv@fuzzy.cz, adarsh.sharma@orkash.com
  Subject: Re: Postgres Performance Tuning
  In-Reply-To: <8b57d989ff79004f9159326f008abefb.squirrel@sq.gransy.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox