Compare framework versions with BenchmarkDotNet

I’m working on upgrading an existing .NET 5.0 application to .NET 6.0. Although the general claim is that .NET 6.0 is (a lot) faster than .NET 5.0, I like to verify if this is correct for my use cases. I have some performance critical code in this application and I have to be sure that performance remains at last on par (and preferably gets better) after the upgrade.

Let's write some micro benchmarks using benchmarkdotnet.

Compare framework versions

I don’t want to make this a full benchmarkdotnet tutorial. If you are new to the library, check out the Getting Started section in the documentation. Let us focus on how we can run a benchmark against multiple framework version.

First thing that is important to do is that our benchmark application (a .NET Core console application) should target all the frameworks we want to test. Therefore update the TargetFrameworks property:

Now we need to update our Program.cs file to call the BenchmarkSwitcher:

Based on the command line parameters we provide,BenchmarkDotNet will generate, builds and executes a new console app per every benchmark using different framework versions.

To run the benchmark comparing performance on .NET 5 and .NET 6, you should execute the following command:

dotnet run -c Release -f net5.0 --runtimes net5.0 net6.0

This will build the benchmarks application in release configuration targeting the .NET 5 surface area, and then run all of the benchmarks on both .NET 5 and .NET 6.

More information: https://benchmarkdotnet.org/articles/configs/toolchains.html

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...

The art of simplicity

Search This Blog