NotificationQueueBenchmark multi consumer benchmarks
Summary: NotificationQueue, although mostly not used as such, is a multi consumer queue and it's missing benchmarks for that part. There where also a couple of issues with original benchmark which this diff addresses: 1. Benchamrks used to do N * number of producers number of iterations and didn't report increased iteration count back to benchmark 2. Benchmark would not run the same case during whole benchmark time as producers where stopped as soon as they produced enough request and consumer would finish without contention Since these are very tight loops I added a busy loop param which can be varied the same way as batching parameter. This param adds some work in a form of a busy loop in both producers and consumer to make benchmarking cases, where producers/consumers are actually doing something except from posting to the queue, easier. Reviewed By: yfeldblum Differential Revision: D16071580 fbshipit-source-id: c75f2dd9ae8617be09834cdf153a4b4ae06aaaca
Showing
Please register or sign in to comment