3 ms·
Larger stacks is a larger buffer. Just as the network can only have a relatively small amount of traffic actually "in flight" but lots can be stuck in buffers
by tialaramex 5y ago
Larger stacks is a larger buffer.
Just as the network can only have a relatively small amount of traffic actually "in flight" but lots can be stuck in buffers - so likewise only a relatively modest amount of containers can be on ships in the ocean.
You need a buffer or every little inconsistency reverberates and it gets out of hand, but bufferbloat shows how too much buffering makes things worse not better. If your metrics say (and some trivial metrics do) that the huge buffer is better, your actual experience contradicts that as everything feels like you're wading through molasses.
I don't have any relevant expertise to judge what the right metrics are for international shipping, but it certainly raised my eyebrows that "Let's make the buffer bigger" is seen as automatically a good idea.
Of course, a network buffer is very different from a container port's stacks, maybe this genuinely is going to make a huge difference. I think more likely it turns out to make no real difference, but can be portrayed as a genius idea that just wasn't embraced wholeheartedly enough to be effective.
- salawat 5y agoMmmm. Doesn't necessarily hold as packets don't exist sans payload. You'd have to add an extra layer on top of the TCP logic to represent the logistical processes involved with moving packets to be filled with payload which are themselves not payload to places they are to be filled. In a way, it sets off more token ring-ish bells for me for some reason.