Open AleksLigeza opened 3 months ago
This is because [IterationSetup]
causes the benchmark method to be invoked only once. Removing it allows it to be invoked multiple times. There are background allocations that we cannot control (see https://github.com/dotnet/runtime/issues/101536), and more benchmark invocations drowns those out.
Hello! I would like to report that using [IterationSetup] is causing 400B to be allocated. I quickly checked how it works for earlier versions and it seems that the problem started in 0.13.6 and persists in 0.13.12.
Please check the summary and code below:
If I remove IterationSetup or change it to GlobalSetup, the problem does not occur.
Thanks!