Re: Memory limits and PostgreSQL 8.4 - Over 63 GB of memory for DB? - Mailing list pgsql-admin

From Nicholson, Brad (Toronto, ON, CA)
Subject Re: Memory limits and PostgreSQL 8.4 - Over 63 GB of memory for DB?
Date
Msg-id 2626AEE4839D064CB0472A3814DC403F46D208131C@GVW1092EXB.americas.hpqcorp.net
Whole thread Raw
In response to Re: Memory limits and PostgreSQL 8.4 - Over 63 GB of memory for DB?  (Tapio Pitkäranta <Tapio.Pitkaranta@relex.fi>)
Responses Re: Memory limits and PostgreSQL 8.4 - Over 63 GB of memory for DB?  (Tapio Pitkäranta <Tapio.Pitkaranta@relex.fi>)
List pgsql-admin
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-
> owner@postgresql.org] On Behalf Of Tapio Pitkäranta
> Sent: Friday, March 18, 2011 4:10 AM
> To: Devrim GÜNDÜZ
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Memory limits and PostgreSQL 8.4 - Over 63 GB of
> memory for DB?
> 
> Hello,
> 
> Thank you for the reply. It seems you might be right:
> 
> /etc/sysctl.conf
> 
> # Controls the maximum shared segment size, in bytes
> kernel.shmmax = 68719476736
> 
> # Controls the maximum number of shared memory segments, in pages
> kernel.shmall = 4294967296
> 
> We have tried to set shared_buffers over 63 GB.
> 
> Do you have any advice on memory settings for servers with large
> amounts of memory (100-200GB)? It seems there is not too much
> documentation on that in the net.

This is unlikely to work out as you expect.  Values for shared buffers over the 8-10GB range aren't recommended.  It
mayneed to be much lower, depending on your workload. 
 

As far as recommendations - try and gauge the size of your working data set and size the shared buffers for that.  From
there- test with your workload, and watch out for checkpoint spikes.
 

Unused memory will still be available to the filesystem to cache data there.

Brad.


pgsql-admin by date:

Previous
From: Tapio Pitkäranta
Date:
Subject: Re: Memory limits and PostgreSQL 8.4 - Over 63 GB of memory for DB?
Next
From: Stephen Rees
Date:
Subject: Re: Backup hot-standby database.