Operating Systems - Thrashing - Working Set Model & Prevention
Identify the misconception in this statement: "The working set model guarantees thrashing will never occur if each process is allocated frames equal to its working set size."
Identify the misconception in this statement: "The working set model guarantees thrashing will never occur if each process is allocated frames equal to its working set size."
medium🐞 Bug Identification Q7 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand working set dynamics
Working set size varies over time; fixed allocation may lag behind changes.Step 2: Analyze options
A: Incorrect, page replacement alone cannot always prevent thrashing.
B: Thrashing is mainly due to paging, not CPU scheduling.
C: Working set size changes dynamically, so fixed allocation may become insufficient.
D: Processes may not use all allocated frames at all times.Final Answer:
Option B -> Option BQuick Check:
Working set size changes, fixed allocation can cause thrashing [OK]
Quick Trick: Working set size is dynamic, fixed frames may be insufficient [OK]
Common Mistakes:
MISTAKES- Assuming fixed allocation always matches working set size
- Confusing CPU scheduling effects with thrashing causes
- Believing page replacement algorithms alone prevent thrashing
Trap Explanation:
PITFALL- Candidates often overlook working set size variability and assume static allocation suffices.
Interviewer Note:
CONTEXT- Tests awareness of working set size dynamics and allocation limitations.
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