CodSpeedHQ/codspeed-cpp - CodSpeed

codspeed-cpp

Blog Docs Changelog

Performance History

Latest Results

fix: exclude paused sections from instrumentation measurement

main

9 days ago

fix: exclude paused sections from instrumentation measurement

cod-2033-codspeed-cpp-includes-setupteardown-in-instrumentation-mode

9 days ago

fixup! fix: exclude paused sections from instrumentation measurement

cod-2033-codspeed-cpp-includes-setupteardown-in-instrumentation-mode

9 days ago

fixup! fix: exclude paused sections from instrumentation measurement

cod-2033-codspeed-cpp-includes-setupteardown-in-instrumentation-mode

9 days ago

fix: exclude paused sections from instrumentation measurement

cod-2033-codspeed-cpp-includes-setupteardown-in-instrumentation-mode

9 days ago

ref: exclude benchmark harness from measurement via collection steady-state Toggle callgrind collection off once at process start and make the PauseTiming()/ResumeTiming() toggles unconditional. Collection is now only enabled inside the benchmark loop, so State setup, timer reads and instrument-hooks zero/dump requests no longer appear in the measurement, and the codspeed_in_benchmark_loop_ gating flag is no longer needed. The toggle is inlined via CALLGRIND_TOGGLE_COLLECT directly (instead of calling the instrument-hooks wrapper) so no toggle frame shows up in flamegraphs; the counted boundary shrinks to the ResumeTiming() epilogue (~6 instructions). SkipWithMessage/SkipWithError restore the toggle parity when a benchmark is skipped mid-loop without pausing. Refs COD-2033

cod-2033-codspeed-cpp-includes-setupteardown-in-instrumentation-mode

12 days ago

ref: exclude benchmark harness from measurement via collection steady-state Toggle callgrind collection off once at process start and make the PauseTiming()/ResumeTiming() toggles unconditional. Collection is now only enabled inside the benchmark loop, so State setup, timer reads and instrument-hooks zero/dump requests no longer appear in the measurement, and the codspeed_in_benchmark_loop_ gating flag is no longer needed. The toggle is inlined via CALLGRIND_TOGGLE_COLLECT directly (instead of calling the instrument-hooks wrapper) so no toggle frame shows up in flamegraphs; the counted boundary shrinks to the ResumeTiming() epilogue (~6 instructions). SkipWithMessage/SkipWithError restore the toggle parity when a benchmark is skipped mid-loop without pausing. Refs COD-2033

cod-2033-codspeed-cpp-includes-setupteardown-in-instrumentation-mode

12 days ago

ref: exclude benchmark harness from measurement via collection steady-state Toggle callgrind collection off once at process start and make the PauseTiming()/ResumeTiming() toggles unconditional. Collection is now only enabled inside the benchmark loop, so State setup, timer reads and instrument-hooks zero/dump requests no longer appear in the measurement, and the codspeed_in_benchmark_loop_ gating flag is no longer needed. The toggle is inlined via CALLGRIND_TOGGLE_COLLECT directly (instead of calling the instrument-hooks wrapper) so no toggle frame shows up in flamegraphs; the counted boundary shrinks to the ResumeTiming() epilogue (~6 instructions). SkipWithMessage/SkipWithError restore the toggle parity when a benchmark is skipped mid-loop without pausing. Refs COD-2033

cod-2033-codspeed-cpp-includes-setupteardown-in-instrumentation-mode

15 days ago

Latest Branches

×72

fix: exclude paused sections from instrumentation measurement#44

9 days ago

e47ecff

cod-2033-codspeed-cpp-includes-setupteardown-in-instrumentation-mode

-9%

chore: bump instrument-hooks#49

22 days ago

29c5f02

cod-2637-bump-instrument-hooks-in-codspeed-cpp-to-support-macos

+16%

Support macos walltime without profiling in codspeed-cpp#48

2 months ago

7146cb6

cod-2459-be-able-to-run-all-integrations-on-macos

© 2026 CodSpeed Technology

Home Terms Privacy Docs