benchmark

Execute Go benchmarks and flag regressions exceeding 10% against a saved baseline.

23|1|Updated Feb 1, 2026

Search Tags:#testing #performance #optimization #go #regression #benchmark

Ready to run

npx skills add https://github.com/PeterBooker/veloria --skill benchmark-peterbooker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/PeterBooker/veloria/tree/main/.claude/skills/benchmark
Command: npx skills add https://github.com/PeterBooker/veloria --skill benchmark-peterbooker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify performance regressions in Go code by running benchmarks and comparing results against a baseline, ensuring code changes do not negatively impact performance.

Core Features & Use Cases

Automated Benchmarking: Executes Go benchmarks with detailed memory and allocation tracking.
Regression Detection: Flags performance degradations exceeding a 10% threshold.
Baseline Comparison: Compares current benchmark results against a saved baseline for trend analysis.
Use Case: After refactoring a critical search algorithm, run this Skill to ensure the changes haven't introduced a performance bottleneck.

Quick Start

Run benchmarks on all packages in the project.

Frequently Asked Questions about benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect performance regressions in Go code?▼

Detect performance regressions in Go by executing benchmarks and comparing current `ns/op`, `B/op`, and `allocs/op` metrics against a saved baseline. The analysis flags any degradations exceeding a 10% threshold.

How do I run Go benchmarks with memory and allocation tracking?▼

Run Go benchmarks with memory and allocation tracking by executing the benchmark tool across performance-critical packages. This captures `B/op` and `allocs/op` metrics to identify potential bottlenecks introduced by recent code changes.

What is the best way to compare Go benchmark results against a baseline?▼

The best way to compare Go benchmark results against a baseline is to save initial metrics and diff them against current results. This trend analysis isolates regressions in operations, memory, and allocations exceeding the 10% threshold.

How does benchmark regression detection work for performance-critical packages?▼

Benchmark regression detection works by targeting performance-critical packages like `internal/index/`, `internal/repo/`, and `internal/api/search/`, running tests, and flagging metric degradations exceeding 10% compared to the saved baseline.

What threshold is used to flag performance regressions in Go benchmarks?▼

A 10% threshold is used to flag performance regressions in Go benchmarks. If current `ns/op`, `B/op`, or `allocs/op` metrics exceed the saved baseline by more than 10%, the analysis flags the degradation.

Can I use benchmark regression detection after refactoring a search algorithm?▼

You can use benchmark regression detection after refactoring a search algorithm to ensure changes haven't introduced a performance bottleneck. It executes targeted Go benchmarks and compares the results against your previously saved baseline metrics.