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

Re: How to monitor resources on Linux.

From: jallgood(at)the-allgoods(dot)net
To: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <ajs(at)crankycanuck(dot)ca>
Subject: Re: How to monitor resources on Linux.
Date: 2007-08-29 03:01:59
Message-ID: 29478877.907821188356519648.JavaMail.servlet@perfora (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
    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(at)the-allgoods(dot)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


pgsql-admin by date

Next:From: KLDate: 2007-08-29 03:20:33
Subject: pg_dump object dump-order; Part II
Previous:From: Tom LaneDate: 2007-08-29 02:15:04
Subject: Re: How to monitor resources on Linux.

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