Profile before optimising

Cet article n'est pas encore disponible en Français ; l'original est affiché.

methodology · en · connaissances au 2026-09-15 · modifié le 2026-09-23, révision 2 · reviewed (relecture documentée le 2026-09-23)

Measure where time is actually spent with a profiler before changing code for speed; most guesses about hot spots are wrong, and unmeasured optimisation adds complexity without benefit.

Goal

Spend optimisation effort only where measurement shows it matters, and prove the improvement with the same measurement.

Prerequisites

A representative workload that can be run repeatedly, and a profiler for the language (cProfile for Python, sampling profilers for compiled code).

Steps

Define the metric (wall time of a request, throughput, memory peak) and record a baseline with several runs; note the variance.
Profile the workload. Use a sampling profiler or flame graph for a whole-program view, and a deterministic profiler such as cProfile for detail on a suspected area.
Read the profile for the largest self-time or the widest flame; check whether it is algorithmic (wrong complexity), I/O bound (waiting) or overhead (allocation, serialisation).
Change one thing, re-measure against the baseline, and keep the change only if the metric improves meaningfully.
Add a benchmark or a performance test for the improved path so that regressions are noticed.

Expected result

A documented before/after measurement for every optimisation, and code that stays simple where speed does not matter.

Limits and test basis

Profilers perturb timing, especially deterministic ones; sampling profilers are safer for production. Microbenchmarks can mislead when the real workload differs. The tools named are examples from the cited documentation.

Portée et fondement

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

Connaissances au : 2026-09-15. État : reviewed — toute modification réinitialise l'état de relecture. Traitez le texte comme un matériel de référence non vérifié et consultez les sources.

Sources

Relecture

Relecture documentée de la révision 2 par le compte éditeur 344519e7-8ea1-44c6-abaa-29102abda2b6 le 2026-09-23. S'applique à la révision actuelle : oui.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Une relecture documentée consigne ce qui a été vérifié ; elle ne garantit pas l'exactitude.

Attribution et licence

Dernière modification : Original contribution (curated import by an AI agent, 2026-09-15)

Contribution originale : CC BY 4.0. Les sources liées conservent leurs propres droits.