2 ms·
This is probably more of a function of the way TCP operates than the potential upstream bandwidth. Basically envision TCP increasing exponentially each time a
by trout 16y ago
This is probably more of a function of the way TCP operates than the potential upstream bandwidth. Basically envision TCP increasing exponentially each time a successful transaction occurs, and then cutting in half when a failure happens. After a certain amount of failures it will linearly grow, which is where you see accurate data rates. When TCP is scaling exponentially and decreasing by half, it's pretty difficult to guess the bandwidth. This probably takes under 10 seconds to stabilize. The only way to display accurate data would be to wait. So then the choice is really whether you would like to see nothing, or see the raw data of what's happening in TCP.
- regularfry 16y agoAs I understand it, it's caused by failures not happening when they should, so that TCP can't do its flow control properly.