メニュー
Run a benchmark with minimal iterations to generate assembly code via BenchmarkDotNet's DisassemblyDiagnoser. Use to generate one big assembly code file per benchmark.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | bench-fast |
| description | Run a benchmark with minimal iterations to generate assembly code via BenchmarkDotNet's DisassemblyDiagnoser. Use to generate one big assembly code file per benchmark. |
/bench-fast <BenchmarkName> [<Runtimes>]
$ARGUMENTS - The name of the benchmark class to run (e.g., LruJustGetOrAdd, LfuJustGetOrAdd, SketchIncrement), optionally followed by a list of one or more runtimes (e.g., net48, net9.0 or net48 net9.0)Run the specified benchmark from BitFaster.Caching.Benchmarks with minimal iterations using BenchmarkDotNet's command line.
Parse the arguments: the first argument is the benchmark name, and the optional second argument is the list of runtimes.
If a runtime arg is specified, execute:
dotnet run -c Release --project BitFaster.Caching.Benchmarks --framework net9.0 -- --runtimes <Runtimes> --filter "<BenchmarkName>" -j short --warmupCount 3 --iterationCount 5 -d --disasmDepth 5
If no runtime is specified, simply omit that command line arg:
dotnet run -c Release --project BitFaster.Caching.Benchmarks --framework net9.0 -- --filter "<BenchmarkName>" -j short --warmupCount 3 --iterationCount 5 -d --disasmDepth 5
The --warmupCount 3 --iterationCount 5 options reduce warmup and iteration counts for faster execution while still executing the code enough times to JIT optimized code.
Generate assembly for code exercised by a benchmark and organize output into a baseline directory named after the current git branch. Use to generate assembly code that can be diff'd between branches.
Split BenchmarkDotNet assembly markdown files into individual files per benchmark method using splitasm. Use to break one big assembly code file per benchmark into one file per benchmark method.