4 ms·
It wasn't dropped or not dropped that was the problem, it was clobbering. If one connection said it had seen 200 events, and another 190, it ping ponged betwee
by hinkley 3y ago
It wasn't dropped or not dropped that was the problem, it was clobbering.
If one connection said it had seen 200 events, and another 190, it ping ponged between them instead of deciding 200+190 = 390. What keeps them from clobbering is distinct tags per connection. If you're running Ruby or Python or Node, that's one connection per thread, and that's ridiculously expensive.