How do you use tracemalloc to find a leak in a Django process?
PICTURE THIS: DJANGO MVT
Simple meaning
Start tracemalloc early, snapshot before and after a request batch, and compare top statistics by traceback.
WHY — Memory instead of guessing?
Why interviewers care about Memory:
question about Memory.
trade-offs, and what you would actually do on a Python 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:
- 1Start tracemalloc early, snapshot
before and after a request batch, and compare top statistics by traceback.
- 2Filter to project frames
so site-packages noise drops.
- 3Combine with queryset iterator()
fixes when the leak is actually a cached QuerySet, not a C-level leak.
- 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
Start tracemalloc early, snapshot before and after a request batch, and compare top statistics by traceback. Filter to project frames so site-packages noise drops.