> IPv4 requests went first, then IPv6, and we recorded the average latency of the 3 requests as the resulting data point (using a float value in milliseconds).
On wifi, the IPv4 requests are going to wake up your radio, and then the latency is going to be better for the IPv6.
On wired, there's very little difference, since there's no radio wakeup delay.
Pinging your default gateway isn't much of a test anyway.
This is great feedback thanks and a very interesting point. Most laptops these days are constantly chatting towards the Internet, just have a look at wireshark! But, the local LAN tests are preceded by IPv4 and IPv6 Internet reachability tests (which the article mentions regarding only taking results from hosts that were concurrently online with dualstack lighthouse reachability. This test suite takes about 7 seconds total and records about 25-30 data points). If we re-run the test we could indeed let IPv6 go first or do them in parallel to account for any sleeping radios.
> IPv4 requests went first, then IPv6, and we recorded the average latency of the 3 requests as the resulting data point (using a float value in milliseconds).
On wifi, the IPv4 requests are going to wake up your radio, and then the latency is going to be better for the IPv6.
On wired, there's very little difference, since there's no radio wakeup delay.
Pinging your default gateway isn't much of a test anyway.