Compute resources for Dremio
Last updated on
Since July, you can order dedicated compute resources for your Dremio instances. They come in different flavors.
Dremio coordinator
Section titled “Dremio coordinator”The coordinator service is responsible for the Dremio UI, the Arrow Flight SQL endpoint and other central tasks. You can’t configure the compute resources of the coordinator.
| Name | vCPUs | Memory (GB) | Instance count |
|---|---|---|---|
| Coordinator | 14 | 64 | 1 |
Dremio engines
Section titled “Dremio engines”In the Dremio context, the run of the queries is delegated to engines. They are a set of computational resources and can be adapted to different use cases. When you order an instance of Dremio at STACKIT, no engine will be created or associated automatically. If you want to use our Dremio engines, you can order them manually.
Available engines for STACKIT Dremio
Section titled “Available engines for STACKIT Dremio”On creation or editing, you can choose CPU and memory of your Dremio engine. Due to a limitation in Dremio, the UI doesn’t reveal the real allocation of vCPUs configured for that size. To mitigate the possibility of creating an invalid configuration, only the 28C-CPU-option is exposed in the UI. You define the real CPU count with the configuration of the size:
| Size | CPU (UI) | vCPUs (applied) | Memory (GiB) | Instance Count | Availability |
|---|---|---|---|---|---|
| STACKIT 2XS | 28C | 7 | 28 | 1 | |
| STACKIT XS | 28C | 14 | 56 | 1 | |
| STACKIT S | 28C | 28 | 112 | 1 | with General Availability |
| STACKIT M | 28C | 28 | 112 | 2 | with General Availability |
| STACKIT L | 28C | 28 | 112 | 4 | with General Availability |