Skip to main content

BenchmarkDotNet - The minimum observed iteration time is … ms which is very small

I created a small benchmark that compared the performance of my application logic with logging enabled vs disabled.

Here is a (simplified) version of my code:

Executed is triggered in the Program.csfile:

However when I executed the benchmark using Benchmarkdotnet, I got the following warnings:

// * Warnings *

MinIterationTime

  NHibernateWithAndWithoutLoggingEnabled.WithLogging: InvocationCount=1, UnrollFactor=1    -> The minimum observed iteration time is 20.9305 ms which is very small. It's recommended to increase it to at least 100.0000 ms using more operations.

  NHibernateWithAndWithoutLoggingEnabled.WithoutLogging: InvocationCount=1, UnrollFactor=1 -> The minimum observed iteration time is 19.2794 ms which is very small. It's recommended to increase it to at least 100.0000 ms using more operations.

You get these warnings when the operation you want to benchmark is very short. As this can lead to unstable results, a warning is produced. To get rid of the warning you should include more operations to increase the execution time.

FIX: For this application I introduced a loop in the benchmark code to execute the same method enough times to reach the minimal suggested timing(100.000 ms).

Labels:

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.
Read more

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         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more