Operating Systems - Thrashing - Working Set Model & Prevention
If a system uses the working set model but still experiences thrashing under heavy load, which advanced technique should be applied next to mitigate thrashing?
If a system uses the working set model but still experiences thrashing under heavy load, which advanced technique should be applied next to mitigate thrashing?
hard🎤 Interviewer Follow-up Q15 of Q15
Step-by-Step Solution
Step 1: Understand why thrashing persists despite working set model
Even with working set allocation, total demand may exceed physical memory.Step 2: Analyze options
A is incorrect because increasing window size may increase working set size, worsening thrashing.
B is correct because load control reduces active processes, lowering total memory demand.
C is incorrect because disabling page replacement is not feasible and increases faults.
D is incorrect because fixed allocation ignores dynamic working sets, risking thrashing.Final Answer:
Option B -> Option BQuick Check:
Load control is the next step after working set model to prevent thrashing under overload.
Quick Trick: Load control = reduce active processes to fit memory
Common Mistakes:
MISTAKES- Thinking increasing working set window helps
- Believing disabling page replacement reduces faults
- Assuming fixed frame allocation solves thrashing
Trap Explanation:
PITFALL- Option A seems plausible as it involves working set tuning, but it can backfire by increasing memory demand.
Interviewer Note:
CONTEXT- Tests expert-level understanding of thrashing prevention beyond basic working set model.
Master "Thrashing - Working Set Model & Prevention" in Operating Systems
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Operating Systems Quizzes