Tim Cassell

@matthew-a-thomas Thanks, I did miss some of that conversation. Also, I started a [discussion](https://github.com/timcassell/ProtoPromise/discussions/157) in my repo about an idea, would love to get your thoughts on it.

I might take a look at implementing this soon. Upon looking at your idea again, I kind of like this. But what would you think about exposing a new interface...

I realized that `GlobalCleanup` can be called multiple times if memory randomization is active. So I think that it will have to be a separate method that runs after `GlobalCleanup`....

@caaavik-msft Do you want to extend the functionality to cover @albahari's needs?

It seems that is expected when methods have not been promoted to a higher JIT tier. For .Net Framework, I'm not really sure, I'm guessing it's just not precise enough...

@Stabzs I did not have async in mind when I wrote that. I'm not sure adding async support would be of much use, though. If your async actions hop to...

> In addition, both allocations and elapsed time tend to be very sporadic when benchmarking async methods. Well that's not surprising if they're hopping to different threads. > Some optimizations...

@Stabzs In the meantime, you could try synchronously waiting on the tasks inside the actions. `task.GetAwaiter().GetResult()`. That's how BDN currently consumes tasks anyway.

No-one has suggested what the API for this should look like yet, so here's my idea. ```cs public class Benchmarks { [ParamsAllValues] public bool MyFlag { get; set; } [Benchmark]...

Another case that should be fixed by #1403.