pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gnanakumar <gnanam@zoniac.com>
To: pgsql-admin@postgresql.org
Subject: Re: Advice/guideline on increasing shared_buffers and kernel parameters
Date: Tue, 8 May 2012 14:56:52 +0530
Message-ID: <00e101cd2cfc$b6140b00$223c2100$@com> (raw)
In-Reply-To: <00da01cd2ce7$35d17780$a1746680$@com>
References: <00da01cd2ce7$35d17780$a1746680$@com>

> did you read
> http://www.postgresql.org/docs/8.2/static/kernel-resources.html ?

Yes, I read.  But I'm not able to find a correct way to increase Linux
Kernel parameters.

> If it is a dedicated DB server the rule of thumb usually is to use 
> 25% RAM for shared buffers, but no more than 8GB unless proper 
> benchmarking has shown a benefit using above 8GB. But I am not 
> sure if 8GB of shared buffers is suitable for 8.2 at all. 8.2 is EOL btw. 
> Also set effective cache size to 50% RAM.

As you can see, in my case, I'm setting only 3 GB (3072 MB), which is 
actually below 8 GB.  So, I need to increase kernel parameters in this 
case. Any ideas/insights?

> Also, do you really NEED 1000 concurrent sessions? IF you really do, it
might 
> be worse to look into a connection pooler. 

Yes, our web-based application has crossed more than 500 concurrent users.
Hence we've already upgraded RAM and now we want to upgrade max connection
parameter too.  Yes, we're already using pgpool-II v3.1.1 for connection
pooling.





view thread (11+ messages)  latest in thread

Message-ID: <00e101cd2cfc$b6140b00$223c2100$@com>
Permalink:  ../00e101cd2cfc$b6140b00$223c2100$@com/
Also on:    postgresql.org/message-id/00e101cd2cfc$b6140b00$223c2100$@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-admin@postgresql.org
  Cc: gnanam@zoniac.com
  Subject: Re: Advice/guideline on increasing shared_buffers and kernel parameters
  In-Reply-To: <00e101cd2cfc$b6140b00$223c2100$@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