mcpField
P
perf-benchmarker

perf-benchmarker

github.com/composio-communityTesting & quality2.0k1.7k installsUpdated 13w ago
Repository

About perf-benchmarker

A skill for running sequential performance benchmarks under defined timing and output rules. It requires warmup, anomaly reruns, and a marked JSON metrics block.

Key features

  1. 01Run benchmarks sequentially
  2. 02Enforce minimum run duration
  3. 03Warm up before measurement
  4. 04Rerun anomalous results
  5. 05Emit metrics as marked JSON

Use cases

  1. 01Measure performance scenarios consistently
  2. 02Produce structured benchmark results

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/composio-community/awesome-claude-plugins --skill perf-benchmarker

After installing, type/perf-benchmarkerin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported