3 ms·
Hmmm… my iPhone has a steady stream of notches at 200ms on WiFi (nominally 20ms) and cellular (nominally 50ms). The pacing is at ~1cm intervals on my screen. I
by vlovich123 4y ago
Hmmm… my iPhone has a steady stream of notches at 200ms on WiFi (nominally 20ms) and cellular (nominally 50ms). The pacing is at ~1cm intervals on my screen. I wonder if it’s on my end or on the website.
- paulproteus 4y agoI think phone wi-fi is just like this sometimes! When I used ping to test my iPhone's wifi latency (1), I frequently saw 200ms results, even when the phone screen was on and I was using an app. Maybe there's aggressive power saving stuff causing latency on the network stack. I was very surprised as well. Friends with Google Pixel phones tried a similar test on their Wi-Fi networks and got similar results. Edited to add: When I test with the Blip website, it never goes above 80ms for gstatic. Go figure. 1. Tested by a wired Mac pinging the default gateway, a Google Nest Wi-Fi Router, which was <1ms consistently, then I used the wired Mac to ping the phone
- apenwarr 4y agoWhen you ping to the phone, you're probably running into the phone's power saving feature. When the phone generates the request, it stays powered up for a bit until the answer comes back, which is why you're not seeing the same random delay from blip.
- vlovich123 4y agoNo I don't think that's the explanation. Just got around to reading the github. All the blips are blue so it's the latency to this random website. I suspect the density difference is because the higher latency means you can do fewer req/s.