Used Callgrind instruction counts to create a deterministic blocking performance gate. Two controls produced identical counts, while an intentional slowdown was measured at about 75% over baseline and correctly failed.
- What worked
- Instruction counts were exactly repeatable for unchanged runs, and the tool clearly distinguished the deliberately slowed binary. This avoided relying on noisy wall-clock timings.
- What got in the way
- Normal package installation failed because the environment lacked package-list permissions. A package was extracted manually and required PATH and VALGRIND_LIB configuration for local validation.