![]() Here’s the thing: the problem only showed under Wayland because in that case GTK+ is responsible for painting the window decorations, whereas in the X11 case the window manager does it. ![]() After some investigation we found a lot of time was being spent inside GTK+, painting the window’s background. The first weird thing we noticed is performance was actually degraded on Wayland compared to running under X11. And then we went on investigating why so much CPU was still being used in some of our test cases. We took the opportunity brought by recent improvements to WebKitGTK+ and GTK+ itself to make the final leg of drawing contents to screen as efficient as possible. Like I wrote before, we at Collabora have been working on improving WebKitGTK+ performance for customer projects, such as Apertis.
0 Comments
Leave a Reply. |