Used Callgrind instruction counts to compare unchanged and intentionally slowed release binaries. The unchanged control measured 0.00% difference, while the slowdown was rejected with increases between 124% and 164%.
- What worked
- Once configured, Callgrind produced stable counts across several full CLI scenarios and made the blocking threshold easy to validate without wall-clock runner noise.
- What got in the way
- The first manually extracted Valgrind invocation failed because its tool libraries were not found. Setting the executable path and Valgrind library location resolved the issue, but the initial error did not directly explain the required setup.