performance-benchmark

Automate ad hoc performance benchmarking for dotnet/runtime code changes.

18.2k|5.5k|Updated Sep 24, 2019
One-click install
npx skills add https://github.com/dotnet/runtime --skill performance-benchmark-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-benchmark
Source: https://github.com/dotnet/runtime/tree/main/.github/skills/performance-benchmark
Command: npx skills add https://github.com/dotnet/runtime --skill performance-benchmark-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates ad hoc performance benchmarking to validate the performance impact of code changes in the .NET runtime.

Core Features & Use Cases

  • Create BenchmarkDotNet benchmarks for changed code paths and run them locally or in CI.
  • Analyze results to identify regressions and compare against baselines.
  • Guidance for producing reproducible benchmarks and running in different environments.

Quick Start

Create a BenchmarkDotNet benchmark for your change and run it with the recommended workflow to obtain immediate results.

Frequently Asked Questions about performance-benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run ad hoc performance benchmarks for dotnet runtime code changes?

Ad hoc performance benchmarking for dotnet runtime changes is automated by creating BenchmarkDotNet benchmarks for modified code paths. You can run these benchmarks locally or in CI to obtain immediate performance results and compare against baselines.

What is the EgorBot benchmarking workflow for posting performance results?

The EgorBot benchmarking workflow is a standardized process for posting benchmark results. This Skill follows the EgorBot workflow to automate ad hoc performance benchmarking and post results during PR reviews for dotnet/runtime code changes.

Can I use BenchmarkDotNet to profile hot paths and identify regressions in PR reviews?

BenchmarkDotNet is used to profile hot paths and identify regressions during PR reviews. The Skill automates creating benchmarks for changed code paths and analyzing results to compare performance across commits and builds.

Do I need BenchmarkDotNet to compare performance across dotnet runtime commits?

BenchmarkDotNet is required to compare performance across dotnet runtime commits and builds. The Skill uses BenchmarkDotNet to generate reproducible benchmarks for changed code paths and analyze results for regressions against baselines.

How do I ensure reproducible benchmarks when profiling dotnet runtime in different environments?

Reproducible benchmarks require following the provided guidance for running in different environments. The Skill offers instructions for creating BenchmarkDotNet benchmarks that produce consistent performance results across local and CI environments.