Why doesn't the linux TOP command show the same amount of memory I configured for the CIS heap size?

Why doesn't the linux TOP command show the same amount of memory I configured for the CIS heap size?

book

Article ID: KB0083256

calendar_today

Updated On:

Products Versions
TIBCO Data Virtualization 7.0.2 and later

Description

TOP shows the total memory used by the Java PIDs. Tibco Data Virtualization (aka TDV or Spotfire ADS) begins with a parent Java PID from our monitor process, and spawns a child Java PID for the main server process. The TOP memory report includes both reserved and allocated memory. The heap size that was configured for TDV (also seen as the JVM's -Xmx) does not set the size of the total Java process. The heap is the amount of memory that the JVM will use for its own object management.
 
There are other things that will consume memory from the OS, such as classes and class loaders, JIT compilers, JNI and other overhead. Memory that has been used will remain reserved for the JVM during its lifetime and the JVM will manage the heap usage as well. TOP will report the total amount of memory that has been reserved by the JVM since it cannot interpret what is actually being actively used in the heap.
  
Keep in mind that beginning with TDV v7, we enforced the mandatory use of a locally based Postgres repository which will also have its own memory requirements. Budget whatever memory is needed for the OS to run without issues. Be aware of any other applications running on the same host.
Given the amount of RAM on the host, choose an appropriate heap size for CIS, leaving enough for the other processes on the host.

Issue/Introduction

This article discusses the memory usage of CIS in the Linux environment.