Skip to main content

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

Popular posts from this blog

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.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Col...