GNOME Bugzilla – Bug 522166
New compositor performs abysmally because of artificial update limit.
Last modified: 2008-03-28 08:37:26 UTC
After installing the new, stable Metacity 2.22.0, I noticed that Iain's newly integrated compositor definitely wasn't performing as well as when I tried it as the separate branch. I investigated, and it appears that in commit revision 3453, an artificial limit is placed on the update rate by adding a timer that only runs every 20ms (50fps), and it will even wait 20ms before updating after a region is marked. This severely hampers the compositor's performance, and makes the image update rate extremely clunky.
Iain was the one who made that change, so he'll presumably be the best person to ask about it.
How does it feel if you change the #if 0 around the timeout at line 1357 to #if 1 so that it uses an idle instead? Does that make it feel snappier?
(In reply to comment #2) > How does it feel if you change the #if 0 around the timeout at line 1357 to #if > 1 so that it uses an idle instead? Does that make it feel snappier? > Yes, actually. I did that when I first identified the issue to make sure it was the cause.
Ok, cool. I've just made the change in SVN. It doesn't make an overly noticable difference on my machine really.
(In reply to comment #4) > Ok, cool. I've just made the change in SVN. It doesn't make an overly noticable > difference on my machine really. > But it noticable here, while moving a window, the redraw is smoother. Thanks Iain