Re:Deep inside the Linux kernel: a network latency spike
by btilly on Thursday November 19, 2015 @07:32PM
(#10598762)
My understanding of the article was that the amount of data that they could be trying to collapse had been up to 32 MB, and now was never more than 2 MB.
Doing a global operation on a large data structure takes longer than doing a global operation on a small data structure. Average throughput may be better if you do that, but maximum latency was the issue here.
Re:Deep inside the Linux kernel: a network latency spike
by acqq on Friday November 20, 2015 @05:53AM
(#10600622)
Thanks, I missed the detail that their maximum buffer size was 32 MB. They speak about the default size but then change the maximum size and show that the longer delays don't happen.
Doing a global operation on a large data structure takes longer than doing a global operation on a small data structure. Average throughput may be better if you do that, but maximum latency was the issue here.