P.S. client-side vsync isn't just a good idea that improves performance on non-buggy drivers [2], but apparently also the norm. It is the design used by gtk and clutter too. I had no idea it was so common till recently.
If you disable client-side vsync in Mir then you take latency backwards [1], and take rendering performance (on mature drivers) backwards [2] [1] https://docs.google.com/spreadsheets/d/1RbTVDbx04ohkF4-md3wAlgmxbSI1DttstnT6xdcXhZQ/pubchart?oid=1566479835&format=interactive [2] https://bugs.launchpad.net/mir/+bug/1388490 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1665802 Title: [regression] mir_demo_client_eglplasma results in 100% cpu and hardly any updates in dragonboard Status in Mir: Opinion Status in Mir 0.26 series: Opinion Status in mesa package in Ubuntu: New Bug description: On a dragonboard 410c, With Mir 0.25 mir_demo_client_eglplasma renders steadily at 15FPS and with low cpu usage. With mir 0.26.1, the process takes 100% cpu (according to top) and frames hardly update on screen, but the client performance is 60-27FPS. To replicate: mir_demo_server --arw-file --launch-client mir_demo_client_eglplasma To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1665802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
