Introduction to HotSpot JVM Performance and Tuning

Edit online

The Sun HotSpot JVM is used when you deploy Sterling B2B Integrator on a Sun Solaris operating system that runs on Sun UltraSPARC processor-based servers and on a Windows operating system.

The HP HotSpot JVM is used when you deploy Sterling B2B Integrator on a HP-UX for IA64 (Itanium) or HP-UX on any other processor.

HotSpot JVMs provide many tuning parameters. There is no golden set of JVM settings that apply to all customers and conditions. Fortunately, the HotSpot JVMs provide good measurement feedback that allows you to measure the effectiveness of the settings. The settings, especially memory settings, are highly dependent on:
  • Transaction mix
  • Amount of data cached
  • Complexity of the transactions
  • Concurrency levels

This topic describes the processes involved in planning, implementing, configuring, monitoring, and tuning the HotSpot Java™ Virtual Machines.

To enable JVM verbose garbage collection, refer to the documentation on JVM parameters for the server in Edit Performance Configuration Settings.

To enable JVM verbose garbage collection for the container JVM, refer to the documentation on JVM parameters for container nodes in Edit Performance Configuration Settings.

For information on the default parameters for the HotSpot JVM, refer to HotSpot JVM Default Parameters.