Compare scheduling algorithms

Run all five algorithms on the same processes and compare their averages side by side. Change the processes on the left and every row updates at once.

Processes

Name Arrival Burst Priority Remove
Length of each slice
Ties at the same momentA process that arrives just as a slice ends joins the queue before the preempted process.
The running process always finishes first.
Highest priority1 is the highest priority.

Averages for the same processes

Algorithm Waiting Turnaround Response Last finish

 

How to read the comparison

Each row runs one algorithm on exactly the processes on the left, with the same quantum for Round Robin and the same priority settings for Priority. The lowest value in each column is marked. Click an algorithm's name to open that schedule in its own simulator, where you can play it step by step and read the reason for every decision.

You will usually notice that the last finish time is the same in every row. None of these algorithms leaves the CPU idle while a process is ready, so they all complete the same total work at the same moment. What changes is who waits along the way, and that is what the averages measure.

Patterns worth looking for

  • SRTF usually has the lowest average waiting time, because it always runs whatever can finish soonest. SJF is close behind when few processes arrive while another is running.
  • Round Robin often has the best response time but a higher average turnaround, because it shares the CPU instead of finishing jobs one at a time.
  • FCFS is the baseline. When a long job arrives first, its waiting times jump; when jobs arrive shortest first, it can match SJF exactly.
  • Priority answers a different question, importance rather than speed, so it can rank last on every average and still be the right choice.

A word of caution

Averages depend heavily on the workload. One set of processes can make any algorithm look good or bad, so try several: the presets, a mix of long and short jobs, and jobs that arrive while others run. The written pages for each algorithm explain why the numbers come out as they do.

Spotted a mistake?

Send the link from "Copy link" with the row that looks wrong.

Email: abdul at abmans dot com