Visit Azul.com Support

Installing Optimizer Hub without Cloud Native Compiler

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

Optimizer Hub can run in different modes:

Before you install, check Kubernetes Requirements to confirm your cluster can accommodate the pods this mode deploys.

Resource Requirements

In ReadyNow-only mode, the pods that serve Cloud Native Compiler are not deployed, so the footprint is smaller than a full installation. The pods you do need are sized the same as in a full installation:

Pod CPU RAM Ephemeral storage

Gateway

7

28GB

1GB

gwProxy

7

1GB

1GB

Management Gateway

2

2GB

1GB

Cache

7

28GB

1GB

For the complete pod list, the full-mode comparison, and guidance on scaling these values for your load profile, see Kubernetes Requirements.

Install Only ReadyNow Orchestrator

To install with only ReadyNow Orchestrator, pass in values-disable-compiler.yaml, together with your values-override.yaml:

 
helm install opthub opthub-helm/azul-opthub \
  -n my-opthub \
  -f values-override.yaml \
  -f values-disable-compiler.yaml

Disabling Cloud Native Compiler on a Full Optimizer Hub Installation

If you installed a full installation of full Optimizer Hub with Cloud Native Compiler and ReadyNow Orchestrator, you can still disable Cloud Native Compiler by:

  • Reinstalling as specified above.

  • Or disable the Cloud Native Compiler globally using the compilations.parallelism.limitPerVm setting, with the value 0, to override the default value of 500.

Note
 Disabling Cloud Native Compiler with compilations.parallelism.limitPerVm alone stops compilation requests but does not remove the Compile Broker pods, so the resource footprint stays the same as a full installation. Reinstall with values-disable-compiler.yaml to reclaim those resources.