NetFabric/NetFabric.Numerics / .agents/skills/dotnet-benchmarking
dotnet-benchmarking
VerifiedMeasure C#/.NET performance with BenchmarkDotNet instead of stopwatches. USE FOR: BenchmarkDotNet console project setup, BenchmarkSwitcher.FromAssembly; [Benchmark]/[Benchmark(Baseline = true)]; [Params]; [GlobalSetup]/[GlobalCleanup]; [MemoryDiagnoser] allocation columns; [BenchmarkCategory]/[GroupBenchmarksBy]/[CategoriesColumn]/[HideColumns]; reading Mean/Error/StdDev/Ratio/Allocated results and BenchmarkDotNet.Artifacts output; avoiding dead-code elimination via return values; comparing .NET runtimes/versions via AddJob/WithRuntime; ManualConfig job classes with WithEnvironmentVariable and RatioStyle.Trend; testing environment-variable variants via .runsettings, `dotnet test -e`/`-s`, Visual Studio run-settings. DO NOT USE FOR: SIMD API selection (dotnet-simd, has its own SIMD-width benchmarking config); LINQ/enumerable tradeoffs (dotnet-enumerable); generic math (dotnet-generic-math).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.6 KB |
| references/comparing-configurations.md | markdown | 2.8 KB |
| references/interpreting-results.md | markdown | 2.7 KB |
| references/runtime-variant-testing.md | markdown | 1.8 KB |
| references/writing-benchmarks.md | markdown | 3.2 KB |
references/comparing-configurations.md
View on GitHub# Comparing Configurations
Use multiple BenchmarkDotNet **jobs** to run the same benchmark methods under different runtimes or environment variables and compare them in one table.
## Comparing .NET Runtimes/Versions
Configure jobs globally in `Program.cs`:
```csharp
using BenchmarkDotNet.Columns;
using BenchmarkDotNet.Configs;
using BenchmarkDotNet.Environments;
using BenchmarkDotNet.Jobs;
using BenchmarkDotNet.Reports;
using BenchmarkDotNet.Running;
var config = DefaultConfig.Instance
.WithSummaryStyle(SummaryStyle.Default.WithRatioStyle(RatioStyle.Trend))
.HideColumns(Column.RatioSD)
.AddJob(Job.Default.WithRuntime(CoreRuntime.Core60))
.AddJob(Job.Default.WithRuntime(CoreRuntime.Core80));
BenchmarkSwitcher.FromAssembly(typeof(Program).Assembly).Run(args, config);
```
- The host runtime must support every job's runtime — the `.csproj` `TargetFramework` must be the same as, or older than, the oldest job runtime.
- Each job re-runs every `[Benchmark]` in the assembly, adding a runtime column to the results.
- `RatioStyle.Trend` renders `Ratio` as `"1.22x faster"`/`"1.90x slower"` instead of a raw decimal — easier to read across many rows.
## Reusable Job Config Classes
For per-class configuration (rather than assembly-wide), define a `ManualConfig` subclass and apply it with `[Config(typeof(...))]`:
```csharp
using BenchmarkDotNet.Columns;
using BenchmarkDotNet.Configs;
using BenchmarkDotNet.Jobs;
using BenchmarkDotNet.Reports;
class MyConfig : ManualConfig
{
public MyConfig()
{
_ = WithSummaryStyle(SummaryStyle.Default.WithRatioStyle(RatioStyle.Trend));
_ = HideColumns(Column.EnvironmentVariables, Column.RatioSD, Column.Error);
_ = AddJob(Job.Default.WithId("Baseline").AsBaseline());
_ = AddJob(Job.Default.WithId("Variant")
.WithEnvironmentVariable("SOME_FEATURE_FLAG", "0"));
}
}
```
```csharp
[Config(typeof(MyConfig))]
public class MyBenchmarks { /* ... */ }
```
`WithEnvironmentVariable(name, value)` launches that job's benchmark process with the variable set — use this to compare any environment-toggled code path (feature flags, GC modes, etc.), not just runtime versions. Guard conditional `AddJob` calls with a hardware/feature capability check when a job only makes sense on supporting hosts, so a job never reports meaningless results for an unsupported configuration.
`Column.EnvironmentVariables` is worth hiding once each job already has a descriptive `WithId(...)` — otherwise the table repeats the same env-var values on every row.
For a ready-made config comparing SIMD widths (`Scalar`/`Vector128`/`Vector256`/`Vector512` jobs via `DOTNET_Enable*` variables), see the `dotnet-simd` skill's `testing-and-benchmarking.md` reference — it's the same pattern applied to SIMD-specific environment variables.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |