Visit Azul.com Support

23.08.0.0

Need help?
Schedule a consultation with an Azul performance expert.
Contact Us

23.08.0.0

Release Notes PDF

Release date: September 11, 2023

This release is based on Azul Prime 23.07.0.0 and corresponds to the following OpenJDK versions:

Major Version OpenJDK Version

8

1.8.0_382-b2

11

11.0.20.1+1-LTS

17

17.0.8.1+1-LTS

What’s New

  • Compilation ranks by priority, which allows the JVM to assign compilation ranks to methods, has been introduced to Azul Prime 23.08.0.0. This allows the Falcon compiler to assign ranks, hot, warm, or cold, to methods in order to prioritize system resources to methods depending on their hotness. The value of compilation ranking is that compiler activity is optimized later in an application run, not only reducing system load and freeing up resources for the running application but also reducing application outliers.

    For more information on compilation ranks, see Analyzing and Tuning Warmup. For newly added options, see Command Line Options.

  • As of Azul Prime 23.08.0.0, ZVision and ZVRobot components have been deprecated and are no longer actively developed. While we still support these components, we encourage users to switch to Java Flight Recorder, as ZVision and ZVRobot are planned for End-of-Life with Azul Prime 24.02.0.0.

  • Support for the latest features in Optimizer Hub (formerly Cloud Native Compiler) 1.8.0. As Cloud Native Compiler expands its scope to offer more functionality than just offloading compilations, it is time to rebrand the offering to better reflect what it does. Starting with release 1.8, we are using the following naming:

    • Optimizer Hub (was Cloud Native Compiler) - The name of the overall component that you install on your Kubernetes cluster.

    • Cloud Native Compiler (was Compiler Service) - The feature that performs the compilation on Optimizer Hub.

    • ReadyNow Orchestrator (was Profile Log Service) - The feature that records and serves ReadyNow profiles to JVMs.

  • In Optimizer Hub 1.8, all major artifacts and command line switches use the updated branding. This includes, but is not limited to:

    If you are using release 1.7 and earlier, all of the previous spellings of artifacts still work. Additionally, all of the pre-1.8 command-line arguments will continue to work for a period of one year from the release of 1.8.

  • The command line option PreferContainerQuotaForVMInternalCPUCount has been set to true by default in order to make calculations of internal thread counts, as well as budgeting options, more clear in container environments.

    In container environments where both CPU shares and CPU quota are specified, such as with Kubernetes where these are commonly specified, the VM now uses quota to calculate compiler and GC thread counts. Prior to Azul Prime 23.08, it was using half of quota for the calculation.

Known Issues

  • There are no new issues to report in this release.

Resolved Issues

Issue ID Description

ZVM-28301

Fix java_lang_String::hash_code

ZVM-28262

Remove default RSS cap for ProfileLogIn

ZVM-28242

JFR profiler does not collect stack traces

ZVM-28144

Exhausting java heap during early VM initialization causes a hang

ZVM-28121

JFR is not collecting jdk.ExecutionSample events on ARM

ZVM-27536

Enable per-thread CPU utilisation data collection in SelfDiagnosticRunLevel=3