Skip site navigation (1) Skip section navigation (2)

Re: Memory reporting on CentOS Linux

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Jeremy Carroll <jeremy(dot)carroll(at)networkedinsights(dot)com>
Cc: "reid(dot)thompson(at)ateb(dot)com" <reid(dot)thompson(at)ateb(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Memory reporting on CentOS Linux
Date: 2009-08-14 20:23:14
Message-ID: dcc563d10908141323qbaf09f7ve08659fe12f88b14@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
I'm betting it's shared_buffers that have been swapped out (2G swapped
out on his machine) for kernel cache.    The RES and SHR being the
same says the actual processes are using hardly any ram, just hitting
shared_buffers.

On Fri, Aug 14, 2009 at 2:20 PM, Jeremy
Carroll<jeremy(dot)carroll(at)networkedinsights(dot)com> wrote:
> But the kernel can take back any of the cache memory if it wants to.
> Therefore it is free memory.
>
> This still does not explain why the top command is reporting ~9GB of
> resident memory, yet the top command does not suggest that any physical
> memory is being used.
>
>
> On 8/14/09 2:43 PM, "Reid Thompson" <reid(dot)thompson(at)ateb(dot)com> wrote:
>
> you're using cached swap in your calculation ( 22825616 )  swap is not
> RAM -- it's disk
>



-- 
When fascism comes to America, it will be intolerance sold as diversity.

In response to

pgsql-performance by date

Next:From: Scott CareyDate: 2009-08-14 20:37:51
Subject: Re: Memory reporting on CentOS Linux
Previous:From: Scott MarloweDate: 2009-08-14 20:21:42
Subject: Re: Memory reporting on CentOS Linux

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group