microbenchmarking

Tool passed security scan

Risky tool definition detected

Redirect all output to a file to avoid consuming context on verbose iteration output: ``` dotnet run -c Release -- --filter "*MethodName" --noOverwrite > benchmark.log 2>&1 ``` Each benchmark method can take several minutes. Rather than running all benchmarks at once, use `--filter` to run a subset at a time (e.g. one or two methods per invocation), read the results, then run the next subset.

Tool passed security scan

Risky tool definition detected

### Output control | Flag | Purpose | |------|---------| | `--artifacts ./path` | Change where results are written | | `--noOverwrite` | Don't overwrite previous result files | | `--exporters json` | Add JSON export (useful for programmatic comparison) | | `--join` | Combine results from multiple benchmark classes into a single table | | `--hide "Error" "StdDev"` | Hide specific columns from the results table | | `--keepFiles` | Keep the generated benchmark project files — useful for debugging b

Tool passed security scan

Tool passed security scan

Tool passed security scan