2 ms·
Really important point: this is measuring baseline latency of sending one packet at a time. They're not measuring latency under load where queueing delays are p
by wtallis 11y ago
Really important point: this is measuring baseline latency of sending one packet at a time. They're not measuring latency under load where queueing delays are possible. The picture there usually looks pretty different and some of the settings they're changing here may be harmful or irrelevant to that case.
- majke 11y agoTotally. Throughput is an enemy of latency. If you have some other applications on that RX queues or CPU's you can't expect any latency numbers.
- brianwawok 11y agoAlso why upstream smart batching is so important. If you only have 1 packet shovel it off. But maybe wait 1-2 micros and see if you can combine 10 packets (up to MTU) to decrease overall latency.
- wtallis 11y agoIt depends some on what layer you're talking about. Nagle's algorithm makes a lot of sense in a lot of situations. But if you've got a complete packet that's ready to encapsulate in an ethernet frame and send over the wire, you only want to try for batching if you're actually hitting a CPU limit from interrupt frequency or something like that. Unless you're dealing with WiFi where extreme amounts of packet aggregation are necessary to get close to the theoretical throughput.
- brianwawok 11y agoWell if you use smart batching ala ( http://mechanical-sympathy.blogspot.com/2011/10/smart-batching.html http://mechanical-sympathy.blogspot.com/2011/10/smart-batchi... ), you don't really have the same kind of hit that you would with Nagle's or a more simple minded batching algo.