pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jignesh K. Shah <J.K.Shah@Sun.COM>
To: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org
Subject: Re: 2GB or not 2GB
Date: Wed, 28 May 2008 22:54:13 -0400
Message-ID: <483E1AD5.1040607@sun.com> (raw)
In-Reply-To: <200805281659.26945.josh@agliodbs.com>
References: <200805281659.26945.josh@agliodbs.com>



Josh Berkus wrote:
> Folks,
>
> Subsequent to my presentation of the new annotated.conf at pgCon last week, 
> there's been some argument about the utility of certain memory settings 
> above 2GB.  I'd like to hash those out on this list so that we can make 
> some concrete recomendations to users.
>
> shared_buffers:  according to witnesses, Greg Smith presented at East that 
> based on PostgreSQL's buffer algorithms, buffers above 2GB would not 
> really receive significant use.  However, Jignesh Shah has tested that on 
> workloads with large numbers of connections, allocating up to 10GB 
> improves performance. 
>   
I have certainly seen improvements in performance upto 10GB using 
EAStress. The delicate balance is between file system cache and shared 
buffers. I think the initial ones are more beneficial at shared buffers 
level and after that file system cache.
I am trying to remember Greg's presentation where I think he suggested 
more like 50% of available RAM (eg in 4GB system used just for 
PostgreSQL, it may not help setting more than 2GB since you need memory 
for other stuff also).. Right Greg?

But if you have 32GB RAM .. I dont mind allocating 10GB to PostgreSQL 
beyond which I find lots of other things that begin to impact..

BTW I am really +1 for just setting AvailRAM tunable for PostgreSQL 
(example that you showed in tutorials) and do default derivations for 
all other settings unless overridden manually.  So people dont forget to 
bump up wal_buffers  or one of them while bumping the rest and trying to 
fight why the hell they are not seeing what they are expecting.

-Jignesh





view thread (12+ messages)  latest in thread

Message-ID: <483E1AD5.1040607@sun.com>
Permalink:  ../483E1AD5.1040607@sun.com/
Also on:    postgresql.org/message-id/483E1AD5.1040607@sun.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: J.K.Shah@Sun.COM, josh@agliodbs.com
  Subject: Re: 2GB or not 2GB
  In-Reply-To: <483E1AD5.1040607@sun.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