I recently run into the issue of the so-called "coordinated omission " when finding out the latency result of wrk doesn't look normal.
Some search leads me to How NOT to Measure Latency and Your Load Generator is Probably Lying to You - Take the Red Pill and Find Out Why, Gil Tene's mail
The argument that a closed-loop load generator doesn't reflect the real world makes sense. But both wrk and wrk2's tactics to solve the omission can't convince me, where they use a fixed maximal connections limit and compensate the CO by a mathematical method that looks like a kind of weighted average(wrk's method). I can't find any solid and formal proof that the method is correct.
Since the coordinated omission problem has already drawn the attention from the benchmark tool community, I really want to know if there's any serious research on this, what's the CORRECT way to avoid it, and are wrk and wrk2's tactics correct?