BenchmarkDotNet icon indicating copy to clipboard operation
BenchmarkDotNet copied to clipboard

Powerful .NET library for benchmarking

Results 338 BenchmarkDotNet issues
Sort by recently updated
recently updated
newest added

https://github.com/dotnet/BenchmarkDotNet/blob/01d9b7889e13cf756068985275a3997217e4a102/src/BenchmarkDotNet/Toolchains/InProcess/NoEmit/InProcessNoEmitExecutor.cs#L59 Currently, benchmarks always run on background thread. It would be great if a new Toolchain and Executor are run on the same thread, or a property is added to...

enhancement
Area:Toolchains

I believe this article is out of date: https://github.com/dotnet/BenchmarkDotNet/blob/master/docs/articles/guides/console-args.md For using a local build of ILC packages it recommends `ilcPath` instead of `ilcPackages`. As far as I can tell, `ilcPath`...

up-for-grabs
Area:Documentation
good first issue

For comparing two Core Runs, the experience is: ```ps1 dotnet run -c Release ` -f net8.0 ` --coreRun "" ` "" ``` Today, it is not possible to compare two...

up-for-grabs
Area:CommandLine

If `--join` is omitted, no error is thrown. Repro: Run this command: ```ps1 dotnet run -c Release -f net9.0 --join --anyCategories Linq ``` Over the [micro benchmarks in dotnet/performance](https://github.com/dotnet/performance/tree/main/src/benchmarks/micro) Error...

bug
up-for-grabs

Upgrading to latest BenchmarkDotNet causes projects with protobuf files to fail. Last known good version is 0.13.12. The difference seems to be related to the newly added parameters for the...

For starters, please excuse me if this is not a bug, but my misunderstanding of what the Ratio value represents. I've created 2 benchmarks, one of them is marked as...

bug
up-for-grabs

Went through #2591 and tried to improve the warning message here - taking a look at what code paths can cause this warning, I see that in `BaseLineCustomColumn.ResultsAreInvalid` it checks...

I have a change that **allows running the benchmarks within Blazor WASM**, but it touches a few things inside the framework, as .NET WASM does not implement System.Process and does...

This strongly-typed enums based implementation is not scaling very well; but for now, lets add 10.0 and soon after lets see if we can make it less verbose to ease...

I recently experimented with the new JetBrains diagnosers. I love the concept. However, I was surprised by how they are implemented. Right now, they attach before the `WorkloadActual` and detach...

Area:Diagnosers