---
title: "Comment by Abhinav Sharma on \"KAI Scheduler Deep Dive: How NVIDIA Schedules GPUs on Kubernetes\" | Hashnode"
description: "The Statement abstraction is the interesting design choice here: treating eviction scenarios as a transaction log with Checkpoint and Rollback keeps the real cl"
url: "https://hashnode.com/posts/kai-scheduler-deep-dive-how-nvidia-schedules-gpus-on-kubernetes/6ad9850f035d0b8ec4de8b8f/comment/6adba150e3a04b494d2d64a9"
---

[Discussion](https://hashnode.com/posts/kai-scheduler-deep-dive-how-nvidia-schedules-gpus-on-kubernetes/6ad9850f035d0b8ec4de8b8f)

Comment [KAI Scheduler Deep Dive: How NVIDIA Schedules GPUs on Kubernetes](https://hashnode.com/posts/kai-scheduler-deep-dive-how-nvidia-schedules-gpus-on-kubernetes/6ad9850f035d0b8ec4de8b8f)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 23](https://hashnode.com/posts/kai-scheduler-deep-dive-how-nvidia-schedules-gpus-on-kubernetes/6ad9850f035d0b8ec4de8b8f/comment/6adba150e3a04b494d2d64a9)

The Statement abstraction is the interesting design choice here: treating eviction scenarios as a transaction log with Checkpoint and Rollback keeps the real cluster untouched until a plan actually works. Pipeline being able to place a pod on resources still held by pods being evicted is what makes same-cycle reclaim practical. The stale-gang grace period is a nice touch too - evicting the surviving pods immediately after one OOM would thrash any busy cluster.
