The previous post is the result of Adi’s question about a particular Oracle process memory (virtual) consumption. Next, “ironman” suggested using “workloads” to answer such question. This resulted in my brain generating the following thought – “is it possible to use workload(s) to restrict consumption of resources” to prevent the “not enough memory to fork a process” message from showing up again? Well, you know what the implication of this message, right? For you who has never seen it the message indicates that it could already be too late to login and all that you can do is reboot the box ……….
Well, we gona try it with Adi sometime next week – I will let you know how did it work. By the way, today on a test LAWSON server, I noticed paging space utilized at 63% (suddenly, and growing) with JAVA being the main offender so this “host/application component” could become a second candidate for using a workload to arrest unlimited resources consumption by an application?
While searching for workload wisdom, I found another little gem which is responsible for the title of this post. I found a document authored by two IBMers Barry J. Saad and Harold R. Lee titled “Methods for Identifying Memory Leaks in AIX Systems“. This document not only sheds light on the heap and memory allocation techniques but it provides tools that every AIX administrator can use to identify the presence of a “leaky” application. The simplicity of this document in comparison to the built-in difficulty and complexity of its scope is simply mind boggling. It takes two subject matter masters to write a technical document that even a preschooler is able to follow and to understand – no kidding.
By the way, the authors use
ps -gv pvid command to obtains the current value (under the SIZE colum) of the virtual memory (RAM + PAGING) used by a process. This value is expressed in units of KB not pages!