Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 1CE5E9FA084 for ; Wed, 29 Aug 2007 00:02:24 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 65537-09 for ; Wed, 29 Aug 2007 00:02:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by postgresql.org (Postfix) with ESMTP id 32B589FA074 for ; Wed, 29 Aug 2007 00:02:02 -0300 (ADT) Received: from pustefix137.perfora.net [172.19.56.141] (helo=pustefix137.perfora.net) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis), id 0MKp8S-1IQDod2d21-0008IN; Tue, 28 Aug 2007 23:02:00 -0400 Message-Id: <29478877.907821188356519648.JavaMail.servlet@perfora> From: jallgood@the-allgoods.net To: Subject: Re: How to monitor resources on Linux. Cc: Cc: Cc: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 X-Binford: 6100 (more power) X-Mailer: Webmail X-Originating-From: 32485842 X-Routing: US X-Message-Id: <32485842$1188356519587172.19.56.14118802318@pustefix137.perfora.net--1143142040> X-Received: from pustefix137.perfora.net by 68.209.119.52 with HTTP id 32485842 for [tgl@sss.pgh.pa.us]; Tue, 28 Aug 2007 23:01:59 EDT Date: Tue, 28 Aug 2007 23:01:59 -0400 X-Provags-ID: V01U2FsdGVkX19zmoBt6T4Ecf91PLX3rn5nlJOADchXBu/SdNU YDFI3a7epPB2UKslmPqPahDubRG1qXwxMjIP8Uy0qAhLKXXg1a mq39lwnmwQ= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/377 X-Sequence-Number: 26708 Hello We have this one app "pcmiler" that ties directly into our backend of our application and will not run in an 64bit enviroment. We had to get ALK to fix some bugs in there code and that is what all the reboots were about mentioned earlier. Put it this way pcmiler was going places in memory it didn't need to go. They did correct the problem. jallgood@the-allgoods.net writes: > This is interesting. We are running a 32bit kernel. On an Opteron? Why in the world are you doing that? > The output from free -l -m. I believe the High and Low are like > watermarks for lack of another word. Uh, no, you are dead wrong. In a 32-bit machine low memory is the first physical GB or so, and high memory is the rest, and there are certain things that have to be in low memory because the hardware won't cope otherwise. Thus, you can run out of lowmem even when there's scads of free memory in highmem. If you've got more than about a GB of physical RAM you need to be running a 64-bit kernel; otherwise you're wasting your hardware. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster