That's explicitly the opposite of what the author says.
"the speed of packets coming into the adapter is 2.5 Gbps. That’s what the router pushes in. The speed going out is around 2 Gbps."
Of course latency is always on the denominator side in the "bandwidth = data / time" equation, but it seems wrong to claim it's latency when it could also be improved by fixing the numerator; it's the entire fraction that's insufficient, thus bandwidth. As written:
"The reason is that if you add up the average time it takes to get the go-ahead through my monitor’s hub, which is around 7.6 µs, to the average time it takes to send 4 KB, around 8.2 µs, you can find what the maximum speed is"
And later, increasing the numerator is exactly what fixes it with the other hardware: "I can see that instead of sending 4 1 KB packets per burst, it would send 8!"
> the chip doesn't have a big enough buffer to keep sufficient packets in flight at once
How does this make sense? Even if his buffer was 100x larger, if the fill bandwidth exceeds the drain bandwidth, it'll eventually fill up. The article says that explicitly:
"Well, if the speed of the drain from my adapter to my Mac is half a gig slower than the speed of the input, then you can imagine the buffer getting filled more and more until it overflows."
"buffer" was perhaps a poor choice of words on my part, because "buffer" is ambiguous. In this case I am referring to the notional "transmit buffer", which is 4 in the non-working case and raised to 8 in the working adapter.
> "I can see that instead of sending 4 1 KB packets per burst, it would send 8!"
Increasing the number of packets in flight does not change the bandwidth, it only improves latency sensitivity (i.e. you can fire more data before requiring an ACK).
> it seems wrong to claim it's latency when it could also be improved by fixing the numerator.
Increasing the bandwidth without increasing the transmit buffer would not fix this issue. The adapter he ends up buying does both (allow 2x the packets in flight, and 2x the bandwidth).
The bottom line here is that the original adapter handles full duplex 2.5g when plugged into the laptop directly, and the SSD gets full duplex bandwidth in excess of 2.5g through the same intermediate link (i.e. the display), so both the adapter and the display have sufficient bandwidth. The added hop of latency however makes the short transmit buffer insufficient to cover the latency.
Then I agree with what you were saying. Those 4 * 1 KiB are a protocol-level size (similar to the TCP window size), not an actual "buffer".
> Increasing the number of packets in flight does not change the bandwidth, it only improves latency sensitivity (i.e. you can fire more data before requiring an ACK).
That I don't fully follow. To me, the measured bandwidth includes all the effects of ACKs etc. If the the protocol demands that you can have at max 4 * 1 KiB unACKed in flight so you're waiting around for ACKs and not snding data, then increasing the number of packets in flight to 8 would 2x the bandwidth.
> The added hop of latency however makes [it] insufficient to cover the latency.
I agree with that, see also my newer reply https://news.ycombinator.com/item?id=50592931
I this context, I also agree with your original statement; I misunderstood what you referring to with "buffer" (meaning the window, not actual storage), and "bandwidth" (where I think you're referring to the 5 Gbit/s nominal bandwidth of the bus, irrespective of the fact that the effective bandwidth of data sent is much lower due to requiring ACKs for small data).