glmark2-wayland is a geometry test so it does not apply. Firefox is a better test, albeit not good. It uses a single OpenGL surface and has no statistics to determine if/when it is dropping frames.
My mrv2 OpenGL program has two OpenGL windows (OpenGL Viewport and a subwindow with an OpenGL Timeline) both updating at 60 FPS (if you provide a 60FPS video) and uses tone-mapping, which makes it way more demanding. Can I ask you to confirm that you do see the issue on your end: - Download mrv2 v1.6.4 from: https://github.com/ggarra13/mrv2/releases/download/v1.6.4/mrv2-v1.6.4-Linux-amd64.tar.gz - Download this sample movie file from: https://mega.nz/file/zWhA3YyA#DMQhnwsYZOemm6hSvfsBGFY4eJb_X1trHOCXcD5VpOE - Run mrv2 on the movie. - Use CTRL + h to bring up the HUD display and select FPS, which will show the actual FPS and drop frames. Ideally, it should show 60FPS and no or little drop frames. Thanks. On the meantime, I'll try to investigate in the FLTK Wayland innards if there's anything wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
