Step 2 of 8 - Virtualization
A runaway query that only affects one tenant
Tenant B fires a runaway query. Tenant A is the neighbour.
Without Cluster Virtualization
- Tenant A, the neighbour
- Tenant B, running the query
- Tenant A p99
- Tenant A errors
- Tenant B p99
With Cluster Virtualization
- Tenant A, the neighbour
- Tenant B, running the query
- Tenant A p99
- 5.6 ms
- Tenant A errors
- 0.0%
- Tenant B p99
- 5.9 ms
Tenant B's virtual cluster throttled.
Read these charts as a table
| Model | Quiet p99 | Peak p99 | Times worse | Peak errors |
|---|---|---|---|---|
| Shared cluster: tenant A | 6.0 ms | 6.4 ms | 1.1x | 0.0% |
| Shared cluster: tenant B | 6.0 ms | 6.1 ms | 1.0x | 0.0% |
| Private Host Cluster: tenant A | 6.0 ms | 5.6 ms | 0.9x | 0.0% |
| Private Host Cluster: tenant B | 6.0 ms | 5.9 ms | 1.0x | 0.0% |
Illustrative, not measured.
Throttle a runaway virtual cluster
September PreviewVirtual cluster receives (and is limited to) a portion of the Private Host Cluster's total available vCPU.
Fair-share vCPU is not a p99 guarantee.
Virtual cluster prioritization
RoadmapAt launch, all virtual clusters receive a fair share of the Private Host Cluster's vCPU. This will allow certain virtual clusters to be prioritized over others.