100
Measuring input latency on Linux: X11 vs Wayland, VRR, and DXVK - Marco Nett (marco-nett.de)
submitted 3 months ago by to c/linux@programming.dev
25 comments fedilink hide all child comments
 

Really cool research. Overall, X11 still wins compared to Wayland(kwin) but only by 0.14 - 0.22 ms. The really bad performance hit is from XWayland which added 3.13 ms.

you are viewing a single comment's thread
view the rest of the comments
[–] -5 points 3 months ago* (1 child)

I'm not saying it does. I'm just saying your argument of 30ms being noticeable is null as blinking is ~10x that.

Anyway your new argument is online competitive play where Ethernet might have 30ms server RTT vs someone with 140ms wireless, sure, bc even if your reaction time is 100ms better than the other guy, he still has a 10ms advantage over you, minimum.

Anyway, now we're all over the place. Look at the figure given in the article that gives a higher level of Total latency

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 11 points 3 months ago

    End to end system latency on a good system is around 15-30ms. I'm saying that I can absolutely tell the difference between end to end system latency of 15-30ms and 60-75ms. Its pointed out and noticed constantly by players and reviewers its one of the biggest strikes against dlss and other framegen. The 100ms network example was an extreme one to highlight that its noticeable even though its "only a blink of an eye".

    If any part of the stack increases input latency it quickly degrades the experience. Lucky 10ms on an already very efficient system does not make Wayland a deal breaker but if that was 30ms difference it would be.

  • permalink
  • fedilink
  • source
  • parent