<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [X regression] aa10text performance reduced ~12% with gnome-session" href="https://bugs.freedesktop.org/show_bug.cgi?id=70948#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [X regression] aa10text performance reduced ~12% with gnome-session" href="https://bugs.freedesktop.org/show_bug.cgi?id=70948">bug 70948</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>> This is an artifact of sending damage events to the compositor quicker. I suspect the issue is that the compositor is rendering more frames during the test rather than the overhead of sending more often I don't follow how just reducing damage event latency would cause more frames to be rendered, unless damage events were earlier clumped more together, so that single compositor update handled multiple events, and now the events are more spread out so that they get handled separately. To validate the assumption of damage events causing the issue, one could e.g. check with xresponse [1] whether the number or timing of damage events changed. [1] <a href="https://maemo.gitorious.org/maemo-tools/xresponse">https://maemo.gitorious.org/maemo-tools/xresponse</a> But if you know what the related changes were and are sure it was latency reduction, notabug sounds fine too.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>