1. The Evolution of Scheduling

The algorithms we studied earlier—First-Come First-Served (FCFS), Shortest Job First (SJF), Priority Scheduling, and Round Robin—were not discarded. They became the engineering foundation upon which today's schedulers evolved.

2. Why Simple Rules Were No Longer Enough

No single, simple scheduling rule can simultaneously satisfy the competing demands of modern computing. Optimizing for one metric almost always degrades another.

3. Today's Operating Systems

Because different devices serve different markets, their operating systems implement vastly different scheduling philosophies.

Linux: Completely Fair Scheduler (CFS) * Goal: Fairness across thousands of concurrent processes. * Philosophy: Instead of managing fixed-priority queues, Linux CFS estimates how much CPU execution time every process has already received. The scheduler then selects the process that has received the least CPU time.

Windows: Dynamic Priority Scheduling * Goal: Instantaneous response for interactive applications. * Philosophy: Windows dynamically boosts the priority of foreground threads (such as clicking a button or typing). Background tasks are temporarily throttled, then boosted once interactive tasks go idle.

macOS: Quality of Service (QoS) based Scheduling * Goal: Silky smooth user experience and interface animations. * Philosophy: Threads are categorized by purpose—User Interactive, User Initiated, Utility, or Background. The scheduler allocates cores and execution windows according to this class structure.

Android: Energy Aware Scheduling (EAS) * Goal: High performance combined with long battery life. * Philosophy: Built on top of the Linux scheduler, EAS estimates the energy consumption of different CPU cores (BIG.little architectures) before dispatching a thread, keeping low-demand work on low-power cores.

RTOS (Real-Time Operating Systems) * Goal: Absolute deterministic execution. * Philosophy: Meeting strict deadlines is more important than fairness. An RTOS will starve all other work on the machine to guarantee that a safety-critical task completes on time.

4. Manthana: The Scheduling Trade-off

Every operating system values something different. If you were designing this system... which scheduling philosophy would you choose?

5. Reflection

The classic scheduling policies taught us how a single processor shares its time. Modern schedulers taught us how to make better decisions under competing constraints.

But we have operated under a silent assumption: that there is only one processor, executing one instruction stream at a time.

Today's computers rarely think with a single core.

They think with many.

And when multiple processors begin working simultaneously, sharing time is no longer the only challenge. The new frontier is sharing memory, coordinating state, and ensuring that processors working in parallel do not step on each other's feet.