3 ms·
I doubt that same-facility RTT has been fixed at 500µs for 30 years. In EC2 us-east-1 I see < 100µs same-availability-zone RTT on TCP sockets, and those have a
by jeffbee 5y ago
I doubt that same-facility RTT has been fixed at 500µs for 30 years. In EC2 us-east-1 I see < 100µs same-availability-zone RTT on TCP sockets, and those have a lot of very unoptimized software in the loop.
function getDCRTT() {
// Assume this doesn't change much?
return 500000; // ns
}
- genewitch 5y agoI show 180-350µs between various machines on my network, all of which have some fiber between them. devices with only a switch and copper between them somehow perform worse, but this is anecdotal because i'm not running something like smokeping! Oh, additionally between VMs i'm getting 180µs, so that looks to be my lower bound, for whatever reason. my main switches are very old, so maybe that's why.
- jeffbee 5y agoAre you measuring that with something like ICMP ping? I think the way to gauge the actual network speed is to look at the all-time minimum RTT on a long-established TCP socket. The Linux kernel maintains this stat for normal TCP connections.
- genewitch 5y agoYes, ICMP ping. I don't have any long established sockets anyhow so i don't know how useful my set of those stats would be.