HW accelerated Xwayland rendering for Nvidia merged

Re:HW accelerated Xwayland rendering for Nvidia merged by kaba0 on Saturday April 10, 2021 @12:12PM (#26762539)

The video is quite old. And I think you should add a compositor on top of i3 to measure the same thing.

The whole point of the talk was that when a compositor is used (which should absolutely be used because with increasing resolutions tearing will just get more visible), X has pretty much a useless role in the whole situation. That is, you’ve got yourself an architectural problem. Which is no surprise, X had been here forever. But maybe it should no longer the be the abstraction we build our graphics on.

[ Parent | on HN ]

Re:HW accelerated Xwayland rendering for Nvidia merged by wander_homer on Saturday April 10, 2021 @12:26PM (#26762651)

With X.org + i3 + picom (GLX backend, animations and vsync enabled) I get: 665.8 ms ± 19.3 ms

So it doesn't seem to have any significant influence either.

[ Parent | on HN ]

Re:HW accelerated Xwayland rendering for Nvidia merged by kaba0 on Saturday April 10, 2021 @12:57PM (#26762939)

Thanks for benchmarking, but as I mentioned, this was/is not a significant problem that would give way for Wayland. What I wrote in the second part of my comment is.

[ Parent | on HN ]