The window says "hey, feel free to send me this many packets, even if I haven't acknowledged them yet". Ideally you want the window to be as big as the number of free slots between you and the recipient.
-
-
This can all be very confusing without the right mental model. Because we generally want one kind of buffer - the window size - to be big, but another kind of buffer - the buffers between links - to be small.
Show this thread -
But if you see the network as train-cars or sushi on a belt, what you can see is that what we *really* want is to fill as many slots as we can when we're sending data! That's really all that's going on.
Show this thread -
One problem with the metaphor: packets don't actually go in loops, they come at the other end, so unlike a sushi belt, there's a kind of off-ramp at each end. Also packets only enter and exit at the ends. There's really no perfect metaphor.
Show this thread -
I'm going to meditate on better metaphors, so that's it for now :)
Show this thread
End of conversation
New conversation -
-
-
I gave a talk at
@Monitorama a couple of years ago about some packet capture visualizations that show things like bufferbloat pretty nicely! Slides: https://speakerdeck.com/dcreager/real-time-packet-analysis-at-scale-monitorama-pdx-2017 … Video:https://vimeo.com/221056132Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.