Manage the Aiven for AlloyDB Omni columnar engine Early availability
Enable or disable the Aiven for AlloyDB Omni columnar engine, and control how much RAM it can use to leverage AI and analytics capabilities of your service.
The Aiven for AlloyDB Omni columnar engine accelerates SQL query processing of scans, joins, and aggregates using Google's AlloyDB Omni columnar engine.
Any change to columnar engine settings results in restarting the service.
Prerequisites
-
Aiven for AlloyDB Omni service running
noteAiven for AlloyDB Omni is in the early availability stage.
-
Access to the Aiven Console
Enable the columnar engine
The columnar engine is enabled by default.
- Log in to the Aiven Console.
- On the Services page, select a service.
- Click Service settings, and go to Columnar engine.
- Click Configure.
- Set google_columnar_engine_enabled to
Enabled
. - Click Save configuration.
Configure the size of the columnar data store
By default, the columnar engine is set to use up to 10% of your service's RAM. You can modify the size of the columnar engine memory to a maximum of 50% of the service's memory.
- Log in to the Aiven Console.
- On the Services page, select a service.
- Click Service settings, and go to Columnar engine.
- Click Configure.
- Set google_columnar_engine_memory_size_percentage to a value between
0
and50
. - Click Save configuration.
Disable the columnar engine
Disable the columnar engine if its design doesn't align well with your workloads or system requirements. Disabling the columnar engine releases resources allocated for the columnar engine.
- Log in to the Aiven Console.
- On the Services page, select a service.
- Click Service settings, and go to Columnar engine.
- Click Configure.
- Set google_columnar_engine_enabled to
Disabled
. - Click Save configuration.