Question
When should a Python developer choose Profiling with cProfile and timeit deliberately?
- Choose Profiling with cProfile and timeit mainly when you want to postpone validation and fix issues manually later.
- Use profiling before rewriting code when the symptom is latency, throughput, or suspicious hot paths in a workflow.
- Choose Profiling with cProfile and timeit whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Profiling with cProfile and timeit only to avoid modeling the real data shape or domain contract explicitly.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: B. Use profiling before rewriting code when the symptom is latency, throughput, or suspicious hot paths in a workflow.
Use profiling before rewriting code when the symptom is latency, throughput, or suspicious hot paths in a workflow. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python