The article walks through the evolution of CPU scheduling from a naïve first‑come‑first‑served queue to priority‑based schemes, explains starvation and time‑slice problems, and shows how tracking each task's actual runtime leads to the Completely Fair Scheduler (CFS) with virtual runtime accounting.
The article walks through the evolution of CPU scheduling—from naïve first‑come‑first‑served queues to priority‑based, time‑slice, and finally the Completely Fair Scheduler—illustrating each approach with code, highlighting pitfalls like starvation, and showing how tracking virtual runtime yields fair and responsive task execution.
This article examines how time‑slice (time‑slot) AB experiments can cause capacity competition, analyzes the resulting bias‑variance trade‑off, and provides practical guidelines for selecting slice lengths and rotation methods to ensure reliable quantitative results while preserving qualitative conclusions.
This article analyses how fixed‑order and random‑order time‑slice carousel designs affect experiment interference, recovery cycles, and data homogeneity through theoretical discussion and extensive simulations, revealing that mixed scheduling rarely shortens cycles and may worsen homogeneity compared to pure fixed‑order approaches.
This article explains how Huolala's data‑science team tackles interference between multiple time‑slice experiments by using city‑level isolation, nested experiment planning, and bias‑variance trade‑offs, providing detailed guidelines, recovery cycles, and case studies to maximize traffic utilization and experimental reliability.
This article explains how modern multi‑core CPUs use time slices, hyper‑threading, and various types of context switching to achieve concurrency, discusses the performance overhead of frequent switches, and offers practical guidelines for optimizing thread count and reducing switching costs.
The article explains how Thread.Sleep works by describing operating‑system scheduling concepts such as time‑slice and preemptive algorithms, answers common questions about Sleep(1000) and Sleep(0), and clarifies why the thread may not resume exactly after the specified delay.
This article explains CPU time‑slice scheduling, defines CPU utilization as T2/T1, and demonstrates through C programs how different loops affect measured CPU usage, showing why multi‑core systems can report over‑100% utilization while single‑core systems cannot.
