1.10.0

Azul Zing Builds of OpenJDK, version 24.08 introduced the new -XX:ProfileName=<name> option that allows a JVM instance to specify a profile name to Optimizer Hub. This name allows multiple JVM instances that use the same profile name to share the Optimizer Hub functionality, such as the use of ReadyNow Orchestrator profiles and Cloud Native Compiler caching.

This new feature also introduces the new command line option -XX:+EnableRNO that enables ReadyNow read and writes in the JVMs against ReadyNow Orchestrator, using ProfileName as the name for the profile log. More info is provided in Using ReadyNow Orchestrator > ReadyNow Orchestrator JVM Options.

The previously used options (OptHubHost and ProfileLogName) is still supported to existing configurations don’t break. But we advise to use the new settings with OptHubHost, EnableRNO, and ProfileName.

Native support for Google Cloud Platform Blob Storage is added. See Installing Optimizer Hub on Google Cloud.

MinIO has been removed from the helm chart as it is mainly intended for testing and demos. For production, cloud-managed blob storage is recommended (AWS S3, Azure Blob Storage, GCP Blob Storage, or S3-compatible (e.g. for Alibaba)).

See Storage Requirements for more info.

The database storage for Code Cache is deprecated because blob storage is the best production-friendly option as it is more scalable, highly available, and durable. At the same time, blob storage is simpler to maintain.

See Optional Database Pod Configuration if you want to keep using the database.

Avoid cleanup of profiles from systems with low restarts by using the last time the JVM requesting that profile was seen alive, rather than the last time the profile was requested.

Improved time-outs for Profile Sync Task. In some configurations with cross-region syncing, the sync task could get stuck because of incorrect configurations. This has been fixed with improved time-outs.

Cross-region syncing of ReadyNow Orchestrator profiles is improved to let new instances check if a later promoted generation becomes available.

Improved the handling of unloaded or unknown classes.

A large amount of stored data may require a significant grace period after a restart of Optimizer Hub to avoid issues with profile download.