pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Shaun Thomas <sthomas@optionshouse.com>
To: Claudio Freire <klaussfreire@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Tons of free RAM. Can't make it go away.
Date: Mon, 22 Oct 2012 13:28:19 -0500
Message-ID: <50859043.7020603@optionshouse.com> (raw)
In-Reply-To: <CAGTBQpZ-+zxkZfkyKr7ZZdfGC6D2FunrZBx3yo4kOwAiD1fzdg@mail.gmail.com>
References: <508583E4.8080102@optionshouse.com>
	<CAGTBQpZA+_fL=D_E0F8jmpdTcTePgkSQGMFEtoWN7OyWuDnOeQ@mail.gmail.com>
	<5085873D.60400@optionshouse.com>
	<CAGTBQpZt76_VwcSAXUSZWRu9c=E4V4mgVA9Y8a-d0cY+ycaYfQ@mail.gmail.com>
	<508589F8.7020808@optionshouse.com>
	<CAGTBQpZ-+zxkZfkyKr7ZZdfGC6D2FunrZBx3yo4kOwAiD1fzdg@mail.gmail.com>

On 10/22/2012 01:14 PM, Claudio Freire wrote:

> You may want to try setting the numa policy before launching postgres:
>
> numactl --interleave=all pg_ctl start

I thought about that. I'd try it on one of our stage nodes, but both of 
them show an even memory split. I'm not sure why our prod node is acting 
this way. We've used bcfg2 so every server has the exact same 
configuration, including kernel parameters, startup settings, and so on. 
I can only conclude that there's something about the activity itself 
that's causing it.

I'll have to take another look after the market closes to see if the 
unallocated chunk shrinks.


-- 
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email




view thread (15+ messages)  latest in thread

Message-ID: <50859043.7020603@optionshouse.com>
Permalink:  ../50859043.7020603@optionshouse.com/
Also on:    postgresql.org/message-id/50859043.7020603@optionshouse.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: sthomas@optionshouse.com, klaussfreire@gmail.com
  Subject: Re: Tons of free RAM. Can't make it go away.
  In-Reply-To: <50859043.7020603@optionshouse.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