In operating systems and CPU scheduling, Burst Time is the total time required by a process to complete its execution on the CPU. It represents the actual "processing" time and does not include the time the process spends waiting in the ready queue or performing Input/Output (I/O) operations.
The Lifecycle of a Process
Most processes alternate between two states:
CPU Burst: The period where the process is actively using the CPU to perform calculations or logic.
I/O Burst: The period where the process is waiting for an I/O device (like reading from a disk or waiting for user input).
Key Characteristics
Process Dependent: Different programs have different burst times. A video editing tool has a high CPU burst time, while a simple text editor has a low one.
Predictability: In real-world systems, the exact burst time is often unknown beforehand. The OS must estimate it based on previous execution history using algorithms like Exponential Smoothing.
Scheduling Input: Burst time is the primary metric used by scheduling algorithms like Shortest Job Next (SJN) and Shortest Remaining Time First (SRTF) to decide which process gets the CPU next.
Example Scenario
Imagine three processes (P1,P2,P3) arrive in the system:
| Process | Burst Time (ms) | Description |
| P1 | 10 | A heavy mathematical calculation. |
| P2 | 3 | A quick system check. |
| P3 | 7 | A data sorting task. |
In this case, the Burst Time for P2 is 3ms. If the OS uses a "Shortest Job First" strategy, it will pick P2 to run before P1 and P3 because it has the smallest burst time.
Comparison with Other Time Metrics
To understand burst time better, it helps to see how it relates to other OS timings:
Arrival Time: When the process enters the ready queue.
Waiting Time: Total time spent sitting in the ready queue.
Turnaround Time: The total time from arrival to completion.
Turnaround Time = Burst Time + Waiting Time
Why It Matters
Efficient CPU scheduling aims to minimize the average waiting time and maximize throughput. By accurately managing processes based on their Burst Times, the OS ensures that the processor isn't "hogged" by one massive task while shorter, interactive tasks are left waiting.