Release Notes of Azul Zing Stream and Stable Builds of OpenJDK

Zing 24.10.0.0 features an update to JVMTI behavior in order to bring it to the modern standard. Previously, a few commercial Java application performance monitoring tools have been reporting too long GC pause times because Zing was reporting non-pausing concurrent GC durations wrongly as GC pauses over JVMTI events JVMTI_EVENT_GARBAGE_COLLECTION_START (GarbageCollectionStart) and JVMTI_EVENT_GARBAGE_COLLECTION_FINISH (GarbageCollectionFinish).

The new correct reporting may increase the actual GC pauses slightly if monitoring software attached with -javaagent using JVMTI is active.

Zing 24.10.0.0 enables the previously implemented command line option OptimizeIdentityHashForDistribution by default. This option implements an optimization to the distribution of identity hash codes. Enabling this option optimizes the protocol for distributing hash codes. Otherwise, some hash table implementations are prone to an unreasonable number of collisions.

The version of libstdc++ packaged with Zing has been upgraded from libstdc++.so.6.0.24 to libstdc++.so.6.0.32.

October 2024 CPU and PSU release security fixes.

There are no new issues to report in this release.

October 2024 PSU release security fixes.

There are no new issues to report in this release.

Internal bug fixes.

There are no new issues to report in this release.

Zing 24.09.0.0 increases the maximum code cache supported from 1758 MB to 4 GB. You can now set both ReservedCodeCacheSize and InitialCodeCacheSize to a value up to 4 GB.

In case you need to disable Extended Native Memory Tracking (NMT), Zing 24.09.0.0 includes new command line option UseExtendedNMT, which you can use to disable Zing’s Extended NMT, and EnableNMTIntegrityChecks, which you can use to disable checks on allocations. Zing runs in Extended NMT mode and includes integrity checks by default. Using -XX:-UseExtendedNMT tells Zing to run NMT in a Zulu-like mode. We do not recommend disabling Extended NMT except in very specific cases.

There are no new issues to report in this release.

The command line option ProfileLogName has been deprecated and replaced with ProfileName. ProfileName supports all existing macros available for ProfileLogName. It is still possible to use ProfileLogName, however, we recommend that you update your configuration in order to guarantee that you have access to all of the latest features implemented in ProfileName.

Note that using ProfileName overrides ProfileLogName, ProfileLogIn, and ProfileLogOut.

Zing 24.08.0.0 introduces a new feature to the Falcon compiler called Multi-Tiering. Multi-Tiering allows Falcon to schedule methods for compilation under different optimization levels, based on method hotness.

Multi-Tiering assigns hot and active methods to final-tier compilation and cold or inactive methods to mid-tier compilation. Final-tier uses the default Falcon optimization level (usually Falcon optimization level 2) while Mid-tier uses Falcon optimization level 0.

Enable Multi-Tiering using the command line option -XX:+UseMultiTiering.

For more information on Multi-Tiering, see Analyzing and Tuning Warm-Up, Using Multiple Compiler Tiers

Zing 24.08.0.0 introduces the ability to apply ReadyNow transformations at runtime. This is done using the newly implemented command line options -XX:ApplyReadyNowTransformations or -XX:ApplyReadyNowTransformationsFile. You can specify which transformations are used on which generation of your ReadyNow profiles.

A transformation profile can be stored on your machine in yaml format and called using -XX:ApplyReadyNowTransformationsFile=//path/to/file.yaml. or you can apply your transformation options directly in the parameters on the command line using -XX:ApplyReadyNowTransformations="\{transformations\:\[\{data: 0\}\]\}".

Zing 24.08.0.0 raises the maximum java heap size (Xmx) supported with non-ZST mode to 14000 GB (14 TB) on Intel Ice Lake and newer x86 processors when 5-level paging (LA57) is enabled at the OS level.

Zing 24.08.0.0 handles requests for PrintJNI without safepoint pause, allowing PrintJNI to run concurrently with your VM process.

July 2024 PSU release security fixes.

There are no new issues to report in this release.

Zing 24.07.0.0 implements an intrinsification of the method java.lang.reflect.Array.get, leading to a significant performance improvement in some cases.

The logic around InlineTree has been greatly improved. This change allows the decisions reached by inlining to be reconstructed on request, instead of running through the tree with each query which sometimes leads to bloated recursive inlinings.

The MXBean PersistentProfileMXBean has been extended with getReadyNowTier1CompilesRate() and getReadyNowTier2CompilesRate(). These methods allow you to see what percentage of compiles are happening in ReadyNow, when compared to all compiles including non-ReadyNow.

July 2024 CPU release security fixes.

There are no new issues to report in this release.

Several methods have been added to Zing MXBean extensions which can request several metrics from a running JVM. The following methods have been added to Zing MXBeans:

CompilationMXBean can return the total number of enqueued and in-progress compilations, and can return the total number of tier 1 and tier 2 compilations at the time of request.

PersistentProfileMXBean can return the ratio of matched or unmatched classes to the number of classes loaded in the VM at the time of request.

You can find a general overview of Zing MXBeans in the Zing MXBeans documentation, or a complete description of all Zing MXBeans methods in the Zing MXBeans API documentation or in the Javadocs included in the Zing documentation bundle found on the Zing customer downloads page.

GC Log Analyzer’s summary page now includes the ID of the current run from Ready Now Orchestrator, listed as Current VM ID.

GC Log Analyzer’s info page now includes the container OS along with the node OS.

Azul Zing 24.06.0.0 includes a significant improvement to Zing’s crash handler which allows it to properly generate diagnostic data when Falcon threads reach stack memory failure.

There are no new issues to report in this release.

April 2024 PSU release security fixes.

The default value of -XX:ProfileStartupLimitInSeconds has changed from 60 to 0. This follows from a previous change where 0 was changed from "infinite" to actually 0 seconds. For more information on ProfileStartupLimitInSeconds, see Command Line Options, Advanced Miscellaneous Options.

Azul Zing 24.05.0.0 implements some behavioral changes to the command line option VMFootprintLevel. In order to reduce memory footprint, malloc arenas now use half the number of CPU cores when setting a non-default value of VMFootprintLevel; L, M, or S

The minimum value supported for Xms (initial heap size) was lowered drastically from 512 MB to 128 MB. Previously, the minimum supported Xms was 512 MB. The minimum supported Xmx (maximum heap size) remains unchanged at 512 MB. The purpose of this change is to reduce memory consumption from small utility processes which don’t require a high amount of memory.

Azul Zing 24.05.0.0 introduces a new command line option, -XX:ThpDisable, which can be used to disable Transparent Huge Pages (THP) in the entire JVM process, even when system THP settings are enabled. When -XX:+ThpDisable is set, THP is turned off, overriding the system default.

Azul Zing 24.05.0.0 is now able to collect Falcon diagnostics during OOM (Out of memory) errors.

Thread-local backoff for secondary_super_cache updates has been ported from OpenJDK, based on JDK-8316180 and is disabled by default. To enable this feature, use the option -XX:SecondarySuperMissBackoff=1000.

A new command line option, OptimizeIdentityHashForDistribution has been introduced in Zing 24.05.0.0. This option enables an alternate implementation for System.identityHashCode() which provides better distribution of objects at the cost of making the identity hash calculation itself slower. This option is disabled by default and can be enabled using -XX:+OptimizeIdentityHashForDistribution.

There are no new issues to report in this release.

Zing 24.04.0.0 implements a new command line option, MallocArenaMax, which is used to define the maximum amount of memory pools available for glibc. The default value is 0.

The command line option UseDefensiveHeapShrinking is now disabled by default in cgroups where memory limiting is set. You can disable this option manually by using -XX:-UseDefensiveHeapShrinking. For more information about defensive heap shrinking, see Command Line Options, Defensive Heap Shrinking.

Zing 24.04.0.0 implements a more efficient way to encode deopt bundles, improving system performance.

Prime JIT compilation logs (LogCompilation) are now fully supported for JITWatch for Zing.

April 2024 CPU and PSU release security fixes.

There are no new issues to report in this release.

In order to establish a better client/server relationship between Zing and Optimizer Hub, Zing now sends its version to Optimizer Hub, making the current version of Zing available and viewable in Optimizer Hub.

There are no new issues to report in this release.

Zing 24.02.0.0 includes new options for defensive heap shrinking. Defensive heap shrinking dynamically reduces committed Java heap in order to avoid Out-of-memory (OOM) errors in container environments, which ordinarily lead to OOM kills and crashes.

You can enable defensive heap shrinking using the flag -XX:+UseDefensiveHeapShrinking. See Command Line Options, Defensive Heap Shrinking for more information on tuning this option:

Specifying VMFootprintLevel enables UseDefensiveHeapShrinking by default.

The C2 Compiler SeaOfNodesC2 has been deprecated in Zing 24.02.0.0. When you use the option -XX:+UseC2, the JVM uses KestrelC2 for C2 compilation.

The command line option UseOptimizedThreadLookup has been disabled by default due to its impact on virtual and physical memory consumption in some cases. This change can negatively effect the lookup times of threads such as with jmm_getThreadCpuTimeWithKind(). The optimization can be turned back on by default with -XX:+UseOptimizedThreadLookup.

Zing 24.02.0.0 implements a significant improvement to code cache segmentation. This improvement makes code cache segmentation elastic instead of fully committing the entire segment, greatly reducing the amount of wasted memory from code cache segmentation.

Following up from our previous deprecation of ZVision and ZVRobot components in Zing 23.08.0.0, we have now removed ZVision and ZVRobot components completely in Zing 24.02.0.0. This means that you are no longer able to use ZVision and ZVRobot with Zing. We recommend using Java Flight Recorder and Azul Mission Control for recording and viewing performance metrics for your JVM.

Zing 24.02.0.0 includes support for Optimizer Hub (formerly Cloud Native Compiler) on ARM64 system architecture.

The compilation ranking feature has been enabled again by default. Compilation ranking was disabled in Zing 23.08.201.0 due to performance issues in particular cases. If you are upgrading from a previous stream release, there is no change in behavior.

There are no new issues to report in this release.

From Azul Platform Prime 24.01.0.0, the garbage collector’s (GC) CPU usage is logged by default. Previously, you had to use the option -XX+:PrintGCDetails. You can view these metrics now by default in GC Log Analyzer in the GC CPU Usage graph. GC CPU Usage is split into 3 metrics, "marking CPU usage," "relocation CPU usage," and "fixup pass," which appear as "New GC Mark," "New GC Reloc," and "New GC Fixup" in the GC CPU Usage graph.

Azul Platform Prime 24.01.0.0 includes a new lightweight, fully functional distribution of the Java Runtime Environment (JRE) for Java 8, 11, 17 and 21. The new Java JREs saves a significant amount of space by removing various debugging options and developer options. The Azul Platform Prime Builds of JRE still fully supports Optimizer Hub and Azul Vulnerability Detection (AVD).

Azul Platform Prime 24.01.0.0 introduces a small but significant change to the behavior of -XX:ProfileStartupLimitInSeconds. Now, when you set this option to 0, it means 0 seconds. Previously, if you set this flag to 0, it would be interpreted as "infinite". You can still specify "infinite" by using any negative number, for example -1. The default behavior without setting this option remains the same, i.e. the default remains 60.

January 2024 CPU and PSU release security fixes.

There are no new issues to report in this release.

Azul platform Prime 23.12.0.0 includes several performance fixes including improvements to handling of arrays such as ArraysFill and ArrayCopy.

More concise logging of the Compilation Ranking feature has been implemented in order to better asses the behavior and impact of this feature. This applies to Falcon compilations only. Newly collected data has been added to the pre-existing charts in GC Log Analyzer, Compiler Statistics > Compiler Queues and Compiler Statistic > Tier 2 Compiler Counts. Newly collected and viewable data includes the following:

There are no new issues to report in this release.

There are no resolved issues to report in this release.

Zing 23.10.0.0 contains the General Availability (GA) release of Azul Prime Builds of OpenJDK 21.

October 2023 CPU and PSU release security fixes, including CPU and PSU fixes for Azul Prime Builds of OpenJDK 21.

There are no new issues to report in this release.

A new option, GPGCSafepointWaitForMutatorResume, has been introduced and is set to true by default. This flag tells the Garbage Collector to pause and wait for mutator threads to be woken up before resuming, after every GC safepoint. If -XX:-GPGCSafepointWaitForMutatorResume is set, the Garbage Collector resumes its work in parallel with mutator threads waking up.

There are no new issues to report in this release.

Compilation ranks by priority, which allows the JVM to assign compilation ranks to methods, has been introduced to Azul Platform 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 Platform 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 Platform 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:

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 Platform Prime 23.08, it was using half of quota for the calculation.

There are no new issues to report in this release.

ZVision and ZVRobot have been separated from the Azul Platform Prime package due to a known vulnerability in jQuery 1.4.3, which is used in building the ZVision and ZVRobot utilities. At this time, Azul is not aware of any vulnerability in ZVision itself. For this reason, ZVision is still available for download for Azul Platform Prime subscribers at https://ftp.azul.com/releases/Zing/ZVision/ZVTools.zip

The command line option -XX:CompileCommand has been updated to use FalconCompileThreshold.

This option is used in the following way:

-XX:CompileCommand="option,<Class>::<method>,FalconCompileThreshold=<threshold value>"

July 2023 CPU release security fixes.