Memory usage of BW applications on Solaris is higher than other platforms.
Article ID: KB0092738
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Memory usage of BW applications on Solaris is higher than other
platforms. Memory usage shown in pmap output is higher than shown
in Jvisualvm.
Symptoms:
1). BW uses higher physical memory on Solaris.
2). The heap usage among different operating systems is the same.
3). BW memory increases after running for a long time. It will reach a limit and memory usage will stop increasing.
See the attachment (Filename: Symptoms.docx) for more details.
Cause:
This is an OS related problem. Heap usage inside JVM is almost the same among different operating systems. But the pmap shows Solaris uses much more RSS than others.
Issue/Introduction
Resolution
The reported memory usage of BW engines on Solaris is normal and expected behavior. Although memory behavior differs from OS to OS, on Solaris memory reclamation happens in a different way. On Solaris, when a number of applications are running, memory is claimed from an existing application's free memory block dynamically. The initial memory footprint will be greater on Solaris. This is why, when comparing the BW engine deployed on Windows, Linux and Solaris, it is Solaris that shows the highest memory usage.
TIBCO applications do have control over memory, but only in the Java heap block of memory. This can be done by various parameters such as ‘java.heap.size.max’, max jobs, flowlimit, etc. TIBCO applications do not have control over other Solaris memory blocks such as generated (JIT:ed) code, loaded libraries (including JAR and class files) control structures for the Java heap, thread stacks and user native memory (malloc:ed in JNI).
Additional Information
Attachments
Feedback
