perf-benchmarker

Solid

Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.

Testing & QA 1,844 stars 519 forks Updated yesterday

Install

View on GitHub

Quality Score: 80/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
39
Issue Health 10%
50
License 10%
0
Description 5%
100

Skill Content

# perf-benchmarker Run sequential benchmarks with strict duration rules. Follow `docs/perf-requirements.md` as the canonical contract. ## Required Rules - Benchmarks MUST run sequentially (never parallel). - Minimum duration: 60s per run (30s only for binary search). - Warmup: 10s minimum before measurement. - Re-run anomalies. ## Output Format ``` command: <benchmark command> duration: <seconds> warmup: <seconds> results: <metrics summary> notes: <anomalies or reruns> ``` ## Output Contract Benchmarks MUST emit a JSON metrics block between markers: ``` PERF_METRICS_START {"scenarios":{"low":{"latency_ms":120},"high":{"latency_ms":450}}} PERF_METRICS_END ``` ## Constraints - No short runs unless binary-search phase. - Do not change code while benchmarking.

Details

Author
composio-community
Repository
composio-community/awesome-claude-plugins
Created
9 months ago
Last Updated
yesterday
Language
JavaScript
License
None

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category