How do you diagnose a thread pool starvation issue?
PICTURE THIS: ASYNC / PROMISE
Simple meaning
Sync-over-async, blocking calls, and too few threads show as delayed requests with low CPU.
WHY — Performance instead of guessing?
Why interviewers care about Performance:
question about Performance.
trade-offs, and what you would actually do on a .NET project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Sync-over-async, blocking calls, and
too few threads show as delayed requests with low CPU.
- 2I remove .Result/.Wait and
use async end-to-end.
- 3How it works
ThreadPool metrics confirm it.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Sync-over-async, blocking calls, and too few threads show as delayed requests with low CPU. I remove .Result/.Wait and use async end-to-end.