perf-benchmarker

仓库创建 2025年10月22日最近提交 2 个月前SkillHot 收录 23 天前
▸ 精选理由

避免并行或过短运行带来的噪声,适合严谨性能验证。

这个 Skill 做什么

按严格规则运行顺序化性能基准以确保测量稳定可靠。

用于跑性能基准测试时保证测量稳定可靠:按顺序(不并行)运行单次基准,先做至少10秒的预热,再以严格的最短时长收集数据(常规60秒,二分查找场景30秒),发现异常会重跑。适合做基线建立、回归验证或对比不同实现的性能。特别在于它强制执行时长和顺序规则,避免短跑或并行导致的噪声。

▸ 展开 SKILL.md 英文原文

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.

开发编程基准测试测量规则稳定性通用
1.8k
Stars
487
Forks
23
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/ComposioHQ/awesome-claude-plugins/master/perf/skills/benchmark/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/ComposioHQ/awesome-claude-plugins/master/perf/skills/benchmark/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# 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 sh
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有