Operating Systems - Semaphore vs Mutex - When to Use Which
You are designing a multi-threaded server where threads must limit concurrent access to a pool of 5 identical database connections. Which synchronization primitive do you choose and why?
You are designing a multi-threaded server where threads must limit concurrent access to a pool of 5 identical database connections. Which synchronization primitive do you choose and why?
hard🌍 Real-world Scenario Q9 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand resource pool constraints
There are 5 identical connections; up to 5 threads can use them concurrently.Step 2: Analyze synchronization options
Mutex (B) protects one resource at a time, but managing 5 connections individually is complex. Binary semaphore (C) limits to 1 thread, underutilizing resources. Spinlock (D) is inefficient for blocking on resource availability.Step 3: Identify best primitive
Counting semaphore initialized to 5 tracks available connections and limits concurrent access correctly.Final Answer:
Option B -> Option BQuick Check:
Counting semaphore matches resource pool concurrency [OK]
Quick Trick: Counting semaphore tracks multiple identical resources concurrently [OK]
Common Mistakes:
MISTAKES- Using mutex for multiple identical resources without counting
- Using binary semaphore limiting concurrency to 1
- Choosing spinlock for blocking resource management
Trap Explanation:
PITFALL- Candidates often default to mutex or binary semaphore, missing counting semaphore's concurrency control.
Interviewer Note:
CONTEXT- Evaluates practical application of synchronization primitives to resource pools.
Master "Semaphore vs Mutex - When to Use Which" in Operating Systems
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Operating Systems Quizzes