benchmark-optimization-loop
ユーザーがシステムを高速化する必要がある場合、このSkillは構造化された最適化ループを提供します。ベースラインの確立、バリアントの生成、結果の測定、最良の安全なバリアントの選択を支援し、すべての変更が証拠に基づくものにします。パフォーマンスチューニング、レイテンシ削減、コスト最適化に最適です。
npx skills add https://github.com/affaan-m/ecc --skill benchmark-optimization-loopBefore / After 効果比較
1 组このスキルがない場合、ユーザーは経験に頼って手動でパラメータを調整し、構造化されていない試行錯誤を行っていました。最適化サイクルは数時間から数日かかり、結果の再現も困難でした。
このSkillは明確なループを提供します:ベースライン測定、バリアント生成、実験、正当性検証、最良のバリアント選択。ユーザーは数十分で複数のバリアントを比較でき、証拠に基づいた再現可能な最適化が可能です。
Benchmark Optimization Loop
Use this skill to convert "make it 20x faster" or "try 50 recursive optimizations" into a bounded measured loop that can actually improve a system.
Required Baseline
Do not optimize until these exist:
- the operation being optimized;
- the correctness gate that must stay green;
- the metric: wall time, p95 latency, rows/sec, cost/run, memory, error rate;
- the current baseline;
- the search budget: max variants, max time, max spend, max data impact.
If the user asks for an unrealistic target, keep the ambition but make the loop bounded and measurable.
Loop
- Measure the baseline.
- Identify bottlenecks from evidence.
- Generate variants that test one hypothesis each.
- Run variants with the same input shape.
- Reject variants that fail correctness, safety, or reproducibility.
- Promote the fastest safe variant.
- Codify the winning path in a script, command, test, config, or doc.
- Rerun the baseline and winner to confirm the delta.
Variant Table
Track variants like this:
Variant | Hypothesis | Command | Time | Correct? | Notes
baseline | current path | npm run job | 120s | yes | stable
batch-500 | fewer round trips | npm run job -- --batch 500 | 42s | yes | winner
parallel-8 | more workers | npm run job -- --workers 8 | 31s | no | rate limited
Recursive Search
For recursive or hyperparameter work:
- persist every run to a ledger;
- compare against the prior accepted winner, not only the previous run;
- keep a holdout or replay check;
- stop when improvement is within noise, correctness fails, cost exceeds the budget, or the search starts changing more variables than it can explain.
Use phrases like "best measured safe variant" instead of "global optimum" unless the search space was actually exhaustive.
Promotion Gate
A variant cannot become the new default until:
- correctness tests pass;
- the performance delta is repeated or explained;
- rollback is obvious;
- the change is encoded in source control or a durable runbook;
- the final summary includes exact commands and measurements.
ユーザーレビュー (0)
レビューを書く
レビューなし
統計データ
ユーザー評価
この Skill を評価