compiz team mailing list archive

[Launchpad Bug Tracker <797741@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

Looking into http://blog.fishsoup.net/2011/06/13/benchmarking-
compositor-performance/ it seems as though we are doing a few things on
damage events in compiz:

 * handle damage
 * reset paint clock to process next redraw at 1/framerate interval
 * repaint scene
 * wait for vblank
 * glXSwapBuffers

My guess is that we want to be able to do sane frame limiting while also
hitting the vblank on time. The frame limiting stuff is rather primitive
in that we wait for the 1/framelimit interval before redrawing the
screen. It might be more useful to immediately redraw the screen in
antcipation of the next vblank and keep the timer running to *cap* these
redraws if they're going over the frame limit.

** Affects: compiz
     Importance: Medium
     Assignee: Sam Spilsbury (smspillaz)
         Status: Confirmed

** Affects: compiz (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: compiz
-- 
compiz paint clock needs to be smarter
https://bugs.launchpad.net/bugs/797741
You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu.