The kernel will not report memory used for caching pages as being unavailable, if a program calls a malloc, the kernel will just swap out the oldest disk page and give the memory to the application.
Your free -mo shows 3 gig free even with cached disk pages. It looks to me more like either a Java problem, or a kernel problem...
On 10/10/05, Jon Brisbin <[EMAIL PROTECTED]> wrote:
Tom Lane wrote:
> Are you sure it's not cached data pages, rather than cached inodes?
> If so, the above behavior is *good*.
> People often have a mistaken notion that having near-zero free RAM means
> they have a problem. In point of fact, that is the way it is supposed
> to be (at least on Unix-like systems). This is just a reflection of the
> kernel doing what it is supposed to do, which is to use all spare RAM
> for caching recently accessed disk pages. If you're not swapping then
> you do not have a problem.
Except for the fact that my Java App server crashes when all the
available memory is being used by caching and not reclaimed :-)
If it wasn't for the app server going down, I probably wouldn't care.
NPC International, Inc.
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly