Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 1F9B79FA3BE for ; Tue, 2 Oct 2007 13:51:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 22136-02-3 for ; Tue, 2 Oct 2007 13:51:25 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by postgresql.org (Postfix) with ESMTP id B8BF89F9696 for ; Tue, 2 Oct 2007 13:51:26 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so2253615ugf for ; Tue, 02 Oct 2007 09:51:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=OUXtsHqgW1Oh/9tPNf5HXZGKD4Fvl7hH3bUSlJnuFIg=; b=gP1dtwmBBaz2I7i3izBSCLfHEh+U5AfUgkehwAV1a0xFlJE19bhHmavjWsmd2tBDOZgg/fPAzCpDjXADeOfclYV8VIIpxusEHOsXsvd25ZhrjLF163t7PoqOlJSc0xLvvDiXm5S2ugm/soY4mazB4wwMpSOwZ/cqkGldYrJVH+A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JBD/65E/bsc0Xt7+9bwcUSY5ePPKSc2Aj2e3YrH5jimE8T6zwtvpOTkCSEepVLSw5WEQyGaFoqIAagVVcVDpOLOvcMgKMoWovSmEWt3tVDmIsxTPtIDv1rhwo27hUq1hoRArOc413zkXbs4raSS6KbqXlCyc4zE70RSH1rQ54EQ= Received: by 10.67.106.19 with SMTP id i19mr1221829ugm.1191343884185; Tue, 02 Oct 2007 09:51:24 -0700 (PDT) Received: by 10.66.220.7 with HTTP; Tue, 2 Oct 2007 09:51:23 -0700 (PDT) Message-ID: Date: Tue, 2 Oct 2007 11:51:23 -0500 From: "Scott Marlowe" To: Decibel! Subject: Re: Linux mis-reporting memory Cc: "Gregory Stark" , "Csaba Nagy" , pgsql-performance@postgresql.org In-Reply-To: <094E11EB-8F17-4C96-993A-4AD637404F91@decibel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070920230400.GM95343@decibel.org> <16213.1190329934@sss.pgh.pa.us> <87r6ksa1jb.fsf@oxford.xeocode.com> <1190363401.4661.116.camel@PCD12478> <87r6ksuzf8.fsf@oxford.xeocode.com> <094E11EB-8F17-4C96-993A-4AD637404F91@decibel.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/3 X-Sequence-Number: 27025 On 10/2/07, Decibel! wrote: > On Sep 21, 2007, at 4:43 AM, Gregory Stark wrote: > > "Csaba Nagy" 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.