That mostly makes sense. Although 20ms swap time is not good because it
means your average frame rate can't exceed 50FPS. There are only 50 lots
of 20ms in a second. You need to allow a couple of milliseconds overhead
to get each frame out so realistically to achieve 60FPS the total frame
time should stay under 14ms.
Certainly Mutter may be to blame, it does have frame scheduling bugs
from time to time. But to prove that we need to see bugs occurring with
FLTK removed from the equation. There must be some other vsync-limited
OpenGL program that has issues in GNOME 50. I've just tried
eglgears_wayland and think that might be exhibiting new issues that
other programs aren't...
** Package changed: ubuntu => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Opinion => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2153492
Title:
Regression in OpenGL Wayland performance (not NVidia issue)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2153492/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
