Performance · interview question

A bug appears around microbenchmarks. What is the strongest first debugging move?

Multiple choiceEasychapter-16-curatedpremiumperformancemicrobenchmarks

python

import timeit

print(timeit.timeit("sum(values)", setup="values=list(range(1000))", number=1000))

Delay clarity until production traffic reveals the edge case and then patch it under pressure.Solve the symptom with comments only and avoid changing the code shape around microbenchmarks.Keep microbenchmarks implicit so the script stays short and hope the next engineer infers the rule.Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.

Answer and explanation

Correct answer

D. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.

Why

That approach is reliable because it creates evidence. A faster microbenchmark can still be irrelevant to the end-to-end user experience.

Test yourself on Performance

A free test with instant, explained results. No account needed.

Start free test

All Performance questions →

A bug appears around microbenchmarks. What is the strongest first debugging move?

Correct answer

Why

More Performance questions