Operating Systems - Thrashing - Working Set Model & Prevention
During a heavy workload, a system using the working set model still experiences thrashing. What is the most likely sequence of events causing this?
During a heavy workload, a system using the working set model still experiences thrashing. What is the most likely sequence of events causing this?
medium🧠🧾 Concept Trace Q4 of Q15
Step-by-Step Solution
Solution:
Step 1: Identify thrashing cause under heavy load
When total working set sizes exceed physical memory, thrashing occurs despite the model.Step 2: Evaluate options
A: Immediate suspension is not typical or practical.
B: Processes' working sets exceeding available frames cause frequent page faults and CPU time loss.
C: Perfect prediction is impossible; thrashing still occurs.
D: Processes do not voluntarily reduce working sets under thrashing.Final Answer:
Option A -> Option AQuick Check:
Working sets exceeding frames cause thrashing despite model [OK]
Quick Trick: Thrashing occurs when total working sets exceed memory [OK]
Common Mistakes:
MISTAKES- Assuming immediate process suspension prevents thrashing
- Believing perfect page prediction is achievable
- Thinking processes self-regulate working set size
Trap Explanation:
PITFALL- Candidates often overestimate system or process control over thrashing under heavy load.
Interviewer Note:
CONTEXT- Assesses understanding of working set model limits under system-wide pressure.
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