GPU clusters for ML training require careful scheduling: each GPU has fixed VRAM, and over-subscribing causes OOM errors. Jobs have different priorities (high-priority fine-tuning vs low-priority batch eval) and different VRAM requirements (4GB for small evals to 38GB for LLM fine-tuning on A100s). Bin-packing schedulers pack jobs onto the fewest GPUs to reduce idle hardware costs; spread schedulers distribute jobs to reduce interference between tenants. This demo simulates an 8-GPU cluster with a priority queue and live job assignment.
Bin-packing: assign each new job to the busiest GPU that still has capacity - maximizes utilization, risks hot-spots
Spread: assign to the least-busy GPU - reduces noisy-neighbor interference, leaves GPUs partially idle
Priority queue: high-priority jobs (fine-tuning, production training) preempt low-priority jobs (batch eval)
VRAM management: each GPU has a fixed memory budget - scheduling must account for both compute and memory
Memory fragmentation: small jobs can fragment a GPU leaving insufficient contiguous memory for large models
A100 80GB GPUs handle full LLM fine-tuning; V100 16GB GPUs handle smaller models and eval workloads
Part of the EngineersOfAI Interactive 3D - free interactive visualizations covering every major concept in machine learning and AI engineering. Hover any element for a plain-English explanation. No code required.