<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Weston almost halves *visible* frame update rate from what application actually produces" href="https://bugs.freedesktop.org/show_bug.cgi?id=106736#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Weston almost halves *visible* frame update rate from what application actually produces" href="https://bugs.freedesktop.org/show_bug.cgi?id=106736">bug 106736</a> from <a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> Daniel Stone</a> <pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=106736#c7">comment #7</a>) > I wasn't able to reproduce the problem with simple-egl test, e.g. with: > weston-simple-egl -b -o -u 15000 > > But that doesn't seem to use *SwapBuffers(). > > I'm not sure whether SwapBuffers() is the only reason why it doesn't trigger > the issue. Maybe the test-case actually need to also fully use GPU, for > this issue to be visible. It certainly does call eglSwapBuffers: <a href="https://gitlab.freedesktop.org/wayland/weston/blob/master/clients/simple-egl.c#L568">https://gitlab.freedesktop.org/wayland/weston/blob/master/clients/simple-egl.c#L568</a> > Just increase the window size W & H parameters until reported FPS is > somewhere between 70-100 FPS. So presumably it's running with eglSwapInterval(0) which doesn't block on frame callbacks at all? > -> I assume in that particular case, compositor would also require higher > GPU priority than the test. Setting priorities is fairly new Mesa (and i915 > kernel module) feature. We do use it: <a href="https://gitlab.freedesktop.org/wayland/weston/commit/b678befb6ed055e6c66466505d9195a3cebf8073">https://gitlab.freedesktop.org/wayland/weston/commit/b678befb6ed055e6c66466505d9195a3cebf8073</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>