<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - With Vsync disabled, Weston almost halves *visible* frame update rate, compared to X desktop" href="https://bugs.freedesktop.org/show_bug.cgi?id=106736#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - With Vsync disabled, Weston almost halves *visible* frame update rate, compared to X desktop" href="https://bugs.freedesktop.org/show_bug.cgi?id=106736">bug 106736</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>Btw. I'm fine if this bug is wontfixed; the issue is now documented here, there was good discussion about it, and there's the repaint-window workaround. Fullscreen <a class="bz_bug_link bz_status_NEW " title="NEW - DRM backend does not buffer support modifiers for composition bypass" href="show_bug.cgi?id=106732">bug 106732</a> & <a class="bz_bug_link bz_status_NEW " title="NEW - Fullscreen GL applications aren't visible with Xwayland, or there's a panel on top (under Weston)" href="show_bug.cgi?id=106734">bug 106734</a> are the real issues which need to be fixed. I assume that with suitable context priorities, and high enough repaint-window, Weston compositor updates will be OK also for non-fullscreen benchmark windows (public benchmarks measure throughput, not latency, so high repaint-window value is fine for them).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>