JDK-8189773 : [doc] VM Tuning Guide for containerized applications
  • Type: Sub-task
  • Component: docs
  • Sub-Component: hotspot
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-10-23
  • Updated: 2019-01-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
There are many kinds of containerized applications with different performance objectives. E.g., for short-lived apps, start-up time may be more important. Long-running apps may care more about throughput, response time or memory conservation.

With the many VM options (related to GC, compiler, class loading, etc), it becomes a daunting task to pick the best set of values to satisfy the need of each containerized applications. Hence, we should provide a Tuning Guide, which would include:

1. Recommended VM option setting for various *typical* containerized applications;
2. Steps that a developer can take to determine the best VM option settings for their own containerized applications.

We can probably use some of the very good CDS/AOT tuning instructions from Matthew Gilliard of the JFaaS team: http://mjg123.github.io/2017/10/02/JVM-startup.html http://mjg123.github.io/2017/10/04/AppCDS-and-Clojure.html