Hacker News Reader

Comment by kbenson | Hacker News Reader

Don't forget that your input (mouse, keyboard) must travel to the other end before you can start receiving the output that's changed from it. The time from you performing an action to the point where you see that change represented (minus the time to do this locally on the gaming PC) is the actual latency.

It's still probably well within your acceptable tolerances, but worth keeping in mind.

View on HN

Fair point. Though the 7ms I mentioned is broken down into:

- 5ms network latency

- 2ms display latency (includes decoding + vsync latency)

I'm assuming that the mouse/keyboard can begin processing as soon as the network call is done. If true that's about 5ms.

Keep in mind that different mice vary in their latency. Even wired mice can vary from 1.5ms to more than 25ms in click latency [1]. So if you use a low latency mouse over the network, it could be faster than some mice that are plugged in directly.

[1] - https://www.rtings.com/mouse/tests/control/latency

Wow, thank you for the link. Somewhat disappointed that the Razer Viper Ultimate, which advertises lower than wired latiences, is on the low end of overpriced mice, but as a new owner, the lightness of it is night and day with every other mouse I've used.

It's good but not worth 160 USD. I'd recommend the Razer Deathadder or V2 Mini. Just my 2 cents.

Personally I get around that by using input devices connected directly to the host PC and not the display client.

Reply on news.ycombinator.com