Dealing With Contention hard
To save a system under extreme contention, you implement 'Load Shedding'. What is the most effective strategy?
- A Process everything slowly.
- B Restart the servers.
- C Increase the queue size.
- D Prioritize requests. Drop Low-Priority (e.g., Logged out search) requests immediately at the ingress to save resources for High-Priority (e.g., Checkout) requests.
Answer: D. Prioritize requests. Drop Low-Priority (e.g., Logged out search) requests immediately at the ingress to save resources for High-Priority (e.g., Checkout) requests.
Queueing during overload only delays the inevitable timeout. Shedding load keeps the good throughput high for critical paths.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Why is 'Exponential Backoff' preferred over constant intervals for retries?
- What is the primary purpose of a Mutex (Mutual Exclusion) lock?
- Why does adding more threads sometimes *decrease* performance?
- In a Saga, if a Compensating Transaction (Undo) fails repeatedly due to contention, what is the last resort?
- In a database, what happens if Transaction A locks a row and Transaction B tries to modify the same row?
- A database restart causes thousands of application servers to instantly try to reconnect. This crashes the DB again. This is called: