Does this mean anything for actual latency, or only bandwidth?
e.g. speed of light could mean a ~40ms ping between LA and Sydney, but best we get today is probably around 150ms?
e.g. speed of light could mean a ~40ms ping between LA and Sydney, but best we get today is probably around 150ms?
Network hops are notoriously slow. In the datacenter the best I have ever seen is 200ns or so per packet which is very rare, most in DC hops are closer to 3-9 usec (especially modular chassis); then you hit the routers. With moderate congestion your routing hops are going to be twice that or more ignoring queuing, and you are likely six hops at least between two points in each direction.
The hollow core stuff mostly will jot help since it gains with distance, but distance means more hops on average, so we are talking about an application where low latency is required but distances are high (where the improvement applies) but the minimum latency achievable is still tens of ms.
It is interesting technology but I think it’s more interesting for hypothetical materials savings than for latency improvement.
There are delays (very small) converting a signal from electrical on one end of the fiber to light and back to fiber on the other end. For this reason, DAC tends to have measurably lower latency compared to fiber for in-rack networking.
The length of an undersea cable is greater than both the straight line and the great circle distance between two points on the earth's surface.
These things do not explain all (probably not even most) of the difference between the latency you suggested and that in the real world, but I hope they help to suggest why the naïve calculation is not achievable.
Curious what you mean by “straight line”; Rhumb line?