Edit for clarity: A total latency of 20ms from motion->display update is not egregiously bad.
But by RTT, I mean the additional latency induced by going to a central server over the internet and back. You've also got latency from input->sensor, sensor->packet, [packet-flight-time], frame-gen-time, [response-packet-flight-time], response-packet->decoded-video, and signal->display-update.
You simply should not put the video feed any further away from your headset than a computer on your desk. Even then, a wired connection gives much better results, because the experience is consistently timed.
But by RTT, I mean the additional latency induced by going to a central server over the internet and back. You've also got latency from input->sensor, sensor->packet, [packet-flight-time], frame-gen-time, [response-packet-flight-time], response-packet->decoded-video, and signal->display-update.
You simply should not put the video feed any further away from your headset than a computer on your desk. Even then, a wired connection gives much better results, because the experience is consistently timed.