vFabric Elastic Memory for Java (EM4J) is designed for customers running virtualized Java applications on vSphere. Focused primarily on memory management and performance analysis, EM4J gives you the insight and power to get the most efficiency and performance out of your virtualized Java applications.
EM4J greatly simplifies the most common configuration and management tasks, such as how to appropriately size virtual machines (VMs) running Java, how to gauge the real memory efficiency of your Java processes over time and how to avoid potential performance problems with configuration alerts.
EM4J also gives you the power to drive further memory efficiencies into your Java workloads by allowing the hypervisor to transparently reclaim memory directly from relatively idle Java Virtual Machines (JVMs), putting them where they are needed most in your virtual infrastructure.
Questions?
1-855-879-8322
1-650-427-3100
EM4J is a monitoring and balloon solution for Java. It contains the following components:
- A JVMTI balloon agent which integrates the JVM with vSphere's resource management capabilities
- A lightweight guest agent which collects JVM usage data in JSON format to publish to the vCenter EM4J monitoring console
- A plug-in to vCenter to display and interpret the data collected from the guest agent
Monitoring
- Displays a list of all Java processes running in a VM within vCenter
- For each Java process, presents configuration options and real-time stats
- For each Java process, displays current memory footprint and usage
- For all Java processes, displays cumulative categories of memory usage and guest paging over time to assist in right-sizing of VMs running Java
- Displays best practice and configuration advice for the VM running Java
- Displays best practice and configuration advice for each Java process
- vCenter alerts and warnings for actual or potential detected performance problems, such as VM too small or excessive guest paging
Ballooning
- Allows either more Java workloads to run in the same host memory or greater headroom with larger JVM heaps and VMs in the same host memory
- JVM balloon agent will inflate a balloon inside the JVM heap if memory pressure exists on the system and if the VM is relatively idle
- JVM balloon heuristics are tuned for all GC policies and heap configurations in Java 6 and Java 7 to be as transparent to the application as possible
- JVM balloon works co-operatively with heap compactions and will contract quickly if the application needs more heap space
- VMs running traditional ballooning can give and take memory from VMs running Java ballooning
- Multiple JVM processes can contribute to a single VM balloon target
- Any performance degradation relative to increased memory pressure is very linear, allowing rapid configuration changes on the fly if required
