Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data. For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.
[docs] Add performance benchmarking guide and contributor guidelines
Address maintainer review feedback for issue #14111.
Changes to docs/performance-benchmarking.md:
- Fix order: MEMBENCH environment variable is set before running benchmarks
- Fix timebenchmark description to explain it skips fast-running benchmarks
- Update benchmark examples to use b.Loop() instead of for i := 0; i < b.N; i++
- Remove b.ResetTimer() as it is not necessary with b.Loop()
- Fix trailing whitespace
Other changes:
- Remove changelog entry (not needed for documentation changes)
cf33fe2
5 days ago
by aviralgarg05
×3.3
Add technical terms to cspell dictionary for performance-benchmarking docs
Added the following terms to the spell-check allowed words list:
- benchtime: Go benchmark time flag
- cpuprofile: Go CPU profiling flag
- flamegraphs: Performance visualization tool term
- MEMBENCH: Memory benchmark environment variable
- memprofile: Go memory profiling flag
- timebenchmark: Custom benchmark timing function reference
- walltime: Wall-clock time measurement term
These terms are used in the new performance benchmarking documentation
and are legitimate technical vocabulary.