<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - drawing performance worse than X" href="https://bugzilla.gnome.org/show_bug.cgi?id=763350#c40">Comment # 40</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - drawing performance worse than X" href="https://bugzilla.gnome.org/show_bug.cgi?id=763350">bug 763350</a> from <a href="page.cgi?id=describeuser.html&login=christian%40hergert.me" title="Christian Hergert <christian@hergert.me>"> Christian Hergert</a> <pre>Created <a href="attachment.cgi?id=324156" name="attach_324156" title="predicted presentation times">attachment 324156</a> <a href="attachment.cgi?id=324156&action=edit" title="predicted presentation times">[details]</a> predicted presentation times I'm going to add some updated patches for cogl and mutter, but I'm unconvinced that we need them yet. Simply applying the gdk-wayland patch above gets us almost all the way there. The reason I'm suggesting not using the cogl and mutter patches will be obvious by looking at the attached graph. Notice how the predicted timing is 25msec across the board. This is what happens when GdkFrameClock can't predict the timing and so it guesses "half-way between frame". 16.7+8.35=25.5 I've been playing around with various tweaks in mutter and cogl and so far have been unable to improve that. I thought that was the original problem and so I focused on it far longer than I'm happy to admit.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>