| eG Monitoring |
|---|
|
Measures reported by WebLogicTest Using the WebLogic server's SNMP interface, this test tracks the rate of requests processed by the server, the number of requests waiting for processing, and the percentage of heap usage by the server. While the rate of requests processed and the number of queued requests can be indicative of performance problems with the WebLogic server, the percentage heap usage can be indicative of the reason for the problem. The heap size determines how often, and for how long garbage collection is performed by the Java Virtual Machine (JVM) that hosts the WebLogic server. The Java heap is a repository for live objects, dead objects, and free memory. When the JVM runs out of memory in the heap, all execution in the JVM stops while a Garbage Collection (GC) algorithm goes through memory and frees space that is no longer required by an application. This is an obvious performance hit because users accessing a WebLogic server must wait while GC happens. No server-side work can be done during GC. Consequently, the heap size must be tuned to minimize the amount of time that the JVM spends in garbage collection, while at the same time maximizing the number of clients that the server can handle at a given time. For Java 2 environments, it is recommended that the heap size be set to be as possible without causing the host system to "swap" pages to disk (use the output of eG's SystemTest to gauge the amount of swapping being performed by the operating system). The measures made by this test are as follows:
|
||||||||||||||||||||||||