The way to benchmark multithreaded actions.

[kayanme]

Consider some object, which should hold a lot of concurrent operations at the same time.
There is the need to benchmark one operation from one thread (still having others working) to verify productivity during parallel load.
The problem is how to correctly hold that background threads still measuring one needed.

I see some ways, but none of them are completely possible now.

1. An ability to run benchmark methods in parallel, so every thread runs its own measuring still providing the needed concurrency.
2. Establish background in setup method. Unfortunatly, there is a need of "unsetup" method, where threads should be stopped.

[AndreyAkinshin]

@kayanme, this is a very great idea. We definitely should add this feature. Unfortunately, it is hard to implement right way. There are a lot of multi-threading side effects like false sharing which can easily spoil a benchmark. We will add it sometimes, but not in the nearest future.

[jmbryan22]

danielpalme/IocPerformance#77

[roji]

Just a big +1 to adding support for properly benchmarking in a concurrent environment - it's super important to be able to see how code behaves under concurrent load (lock contention, CPU caches...). Some knobs would be necessary - number of threads etc.

[spati2]

+1

[nxrighthere]

This should be one of the top priorities, please.

[lydonchandra]

+1

[osjoberg]

+1

[im-aIex]

While not an exact replacement, with the deprecation of the Visual Studio load tests, it would be great to be able to migrate some the loads tests to benchmarks and get some similar data out of it (customize # of 'users'/threads, time per run, etc.).

[kirsan31]

Any news/thoughts on this?