2 ms·
It 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 re
by wtallis 11y ago
It 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.