Memory consumption

The memory consumption service can be periodically checked for memory consumption, memory availability, memory used and total memory available.

The following table lists the available services.

Service

Description

http://{host}:8080/pdweb-idaho/memUtilized

Returns the utilization in percentage

http://{host}:8080/pdweb-idaho/memUsed

Returns the current consumption of the memory in bytes

http://{host}:8080/pdweb-idaho/memAvail

Returns the current available memory in bytes

http://{host}:8080/pdweb-idaho/memTotal

Returns the total memory available to the process

Monitoring these services can help determine the memory usage pattern of the application and whether there is enough memory available for the application. Knowing the utilization value can help foresee the health status of the application, for example, if the current utilization is 95%, it is possible that the application could soon run out of memory and become unresponsive. Although the Java Garbage Collection can be tuned to optimize how the Java process manages memory, it can never guarantee the continuous life of the application in terms of usage/memory. Heavy usage will consume more memory, despite the Java Garbage Collection's attempt to claim the memory back.

Memory statistics can be collected by periodically calling these services. Careful study can help understand whether the system has enough memory for the usage pattern. If it does not, consider upgrading the memory.

The total memory available for Tomcat can be configured as a Java argument, together with other garbage collection parameters.