Re: Linux mis-reporting memory

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: Decibel! <decibel(at)decibel(dot)org>
Cc: "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Csaba Nagy" <nagy(at)ecircle-ag(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Linux mis-reporting memory
Date: 2007-10-02 16:51:23
Message-ID: dcc563d10710020951y6ee76521n7a8e633e7847d7c8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 10/2/07, Decibel! <decibel(at)decibel(dot)org> wrote:
> On Sep 21, 2007, at 4:43 AM, Gregory Stark wrote:
> > "Csaba Nagy" <nagy(at)ecircle-ag(dot)com> writes:
> >
> >> On Fri, 2007-09-21 at 09:03 +0100, Gregory Stark wrote:
> >>>>> Mem: 32945280k total, 32871832k used, 73448k free,
> >>>>> 247432k buffers
> >>>>> Swap: 1951888k total, 42308k used, 1909580k free,
> >>>>> 30294300k cached
> >>>>
> >>> It seems to imply Linux is paging out sysV shared memory. In fact
> >>> some of
> >>> Heikki's tests here showed that Linux would do precisely that.
> >>
> >> But then why is it not reporting that in the "Swap: used"
> >> section ? It
> >> only reports 42308k used swap.
> >
> > Hm, good point.
> >
> > The other possibility is that Postgres just hasn't even touched a
> > large part
> > of its shared buffers.
>
> Sorry for the late reply...
>
> No, this is on a very active database server; the working set is
> almost certainly larger than memory (probably by a fair margin :( ),
> and all of the shared buffers should be in use.
>
> I'm leaning towards "top on linux == dumb".

Yeah, that pretty much describes it. It's gotten better than it once
was. But it still doesn't seem to be able to tell shared memory from
cache/buffer.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Kempter 2007-10-02 17:31:45 performance of like queries
Previous Message Decibel! 2007-10-02 15:57:18 Re: Linux mis-reporting memory