Preemptive and Non-Preemptive Scheduling
Prerequisite – CPU Scheduling
1. Preemptive Scheduling:
Preemptive scheduling is used when a process switches from running state to ready state or from the waiting state to ready state. The resources (mainly CPU cycles) are allocated to the process for a limited amount of time and then taken away, and the process is again placed back in the ready queue if that process still has CPU burst time remaining. That process stays in the ready queue till it gets its next chance to execute.
2. Non-Preemptive Scheduling:
Non-preemptive Scheduling is used when a process terminates, or a process switches from running to the waiting state. In this scheduling, once the resources (CPU cycles) are allocated to a process, the process holds the CPU till it gets terminated or reaches a waiting state. In the case of non-preemptive scheduling does not interrupt a process running CPU in the middle of the execution. Instead, it waits till the process completes its CPU burst time, and then it can allocate the CPU to another process.
Key Differences Between Preemptive and Non-Preemptive Scheduling:
- In preemptive scheduling, the CPU is allocated to the processes for a limited time whereas, in Non-preemptive scheduling, the CPU is allocated to the process till it terminates or switches to the waiting state.
- The executing process in preemptive scheduling is interrupted in the middle of execution when higher priority one comes whereas, the executing process in non-preemptive scheduling is not interrupted in the middle of execution and waits till its execution.
- In Preemptive Scheduling, there is the overhead of switching the process from the ready state to running state, vise-verse and maintaining the ready queue. Whereas in the case of non-preemptive scheduling has no overhead of switching the process from running state to ready state.
- In preemptive scheduling, if a high-priority process frequently arrives in the ready queue then the process with low priority has to wait for a long, and it may have to starve. , in the non-preemptive scheduling, if CPU is allocated to the process having a larger burst time then the processes with small burst time may have to starve.
- Preemptive scheduling attains flexibility by allowing the critical processes to access the CPU as they arrive into the ready queue, no matter what process is executing currently. Non-preemptive scheduling is called rigid as even if a critical process enters the ready queue the process running CPU is not disturbed.
- Preemptive Scheduling has to maintain the integrity of shared data that’s why it is cost associative which is not the case with Non-preemptive Scheduling.
|Parameter||PREEMPTIVE SCHEDULING||NON-PREEMPTIVE SCHEDULING|
|Basic||In this resources(CPU Cycle) are allocated to a process for a limited time.||Once resources(CPU Cycle) are allocated to a process, the process holds it till it completes its burst time or switches to waiting state.|
|Interrupt||Process can be interrupted in between.||Process can not be interrupted until it terminates itself or its time is up.|
|Starvation||If a process having high priority frequently arrives in the ready queue, a low priority process may starve.||If a process with a long burst time is running CPU, then later coming process with less CPU burst time may starve.|
|Overhead||It has overheads of scheduling the processes.||It does not have overheads.|
|Cost||cost associated||no cost associated|
|CPU Utilization||In preemptive scheduling, CPU utilization is high.||It is low in non preemptive scheduling.|
|Waiting Time||Preemptive scheduling waiting time is less.||Non-preemptive scheduling waiting time is high.|
|Response Time||Preemptive scheduling response time is less.||Non-preemptive scheduling response time is high.|
|Examples||Examples of preemptive scheduling are Round Robin and Shortest Remaining Time First.||Examples of non-preemptive scheduling are First Come First Serve and Shortest Job First.|