4 ms·
It's not uncommon for screens to have input latencies in the 50-100ms range - John Carmack tweeted "I can send an IP packet to Europe faster than I can send a p
by jordanthoms 10y ago
It's not uncommon for screens to have input latencies in the 50-100ms range - John Carmack tweeted "I can send an IP packet to Europe faster than I can send a pixel to the screen. How f’d up is that?". [0]
Given that people are generally happy to accept that kind of latency for a frame getting from their GPU to photons, I don't see why an extra ~10ms of latency getting a frame back and forth from a local datacenter would be a dealbreaker except for the most demanding scenarios. It does require that the datacenter is close to the user though.
[0] - https://twitter.com/id_aa_carmack/status/193480622533120001 https://twitter.com/id_aa_carmack/status/193480622533120001 & http://superuser.com/a/419167 http://superuser.com/a/419167
- lithos 10y agoSo because putting a pixel on the screen is slow it's okay to add more time?
- user5994461 10y agoThe latency to the screen is fixed with no jitter. The human mind can adapt. Network latency is erratic and variable, sometimes packets are just lost.
- throwaway7767 10y ago> The latency to the screen is fixed with no jitter. The human mind can adapt. In addition, latency is cumulative and after a certain threshold becomes extremely annoying. Adding network delays to the already-present latency elsewhere in the system just makes you more likely to hit that threshold.