1.9.4

Includes bug fixes for Optimizer Hub 1.9.3.

When using Optimizer Hub with AWS, you can now use an K8S ServiceAccount for S3 permissions. For more info, check out the documentation at Using AWS Service Accounts.

Profile download errors, caused by any reason, are now reflected in metrics and visible in the Grafana dashboard.

Improved stability of the readiness probes for the Optimizer Hub Components.

The limit of incoming connections for single instances of the gateway (Envoy proxy) is increased from 1024 to 3072.

You can now configure the AWS region of S3 with the Helm value storage.s3.region.

Implemented stricter data consistency validation during the upload of RNO profiles to prevent BlobNotFound errors later.

Old Prime JVMs (pre-23.08), using an earlier protocol version, can send profile chunks in an incorrect order. This can lead to some chunks getting lost, e.g., due to reconnections.

With newer Prime JVMs, using the latest protocol, this same issue has been noticed very rarely, and research is ongoing.