# How Netflix Simplified Batch Compute with Kueue

[Netflix](https://yomu.fyi/company/netflix) · Netflix Technology Blog · Jun 22, 2026

**Type:** Problem & solution

## Summary

Netflix transitioned its managed batch compute infrastructure from a homegrown solution called Compute Managed Batch to Kueue on its Titus container platform. CMB previously relied on custom scheduling and admission-only fair sharing without preemption, making feature development cumbersome as the Kubernetes ecosystem evolved. To modernize the platform transparently, Netflix mapped internal tenants to Cohorts and leaf tenants to ClusterQueues and LocalQueues while routing jobs through a custom Kueue router. Kueue operates alongside existing Titus scheduling profiles rather than replacing the kube-scheduler, preserving cluster placement efficiency. The migration was completed in four weeks across millions of batch workloads, significantly increasing average resource utilization through preemption-based fair sharing.

## Context

Netflix originally managed batch workloads on its Titus platform using Compute Managed Batch (CMB), a custom solution built in 2018. Over time, maintaining custom scheduling and queueing logic separate from Kubernetes made implementing features like preemption cumbersome. Additionally, CMB lacked preemption capabilities, meaning admitted jobs ran to completion even when fair-share demand shifted across tenants.

## Approach / What changed

Netflix modernized its infrastructure with Netflix Batch by replacing CMB queuing and scheduling with Kueue across Titus cells. The team mapped CMB internal tenants to Kueue Cohorts and leaf tenants to LocalQueues and ClusterQueues, converting capacity configurations into resource flavors and nominal quotas. Titus federation routes workloads to Kueue cells using a custom Kueue router while preserving existing API surfaces for end users.

## Takeaways

- Kueue was chosen over alternatives like YuniKorn or Volcano because it integrates with existing Titus scheduling profiles without replacing pod scheduling by the kube-scheduler.
- Meeting production throughput requirements required running Kueue with significantly higher QPS, Burst, and groupKindConcurrency settings than the default configurations.
- Migrating the largest and most complex customer first helped build confidence and enabled the team to complete the full production migration within four weeks.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Kubernetes](https://yomu.fyi/topic/kubernetes), [Migrations](https://yomu.fyi/topic/migration), [Scalability](https://yomu.fyi/topic/scalability)

[Read original post](https://netflixtechblog.com/how-netflix-simplified-batch-compute-with-kueue-87860682629c)