What is context switching and why does it cost CPU?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
The OS pauses one thread or process, saves registers and scheduler state, and resumes another.
WHY — OS instead of guessing?
Why interviewers care about OS:
who only read docs from people who shipped.
and tied to Backend work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1The OS pauses one
thread or process, saves registers and scheduler state, and resumes another.
- 2That save and restore
plus cache disruption wastes cycles that could have run your code.
- 3Too many runnable threads
on a Java service increases context switching and latency.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
The OS pauses one thread or process, saves registers and scheduler state, and resumes another. That save and restore plus cache disruption wastes cycles that could have run your code.