Open Bug 1485100 Opened 6 years ago Updated 2 years ago

Consider to lower framerate (vsync rate) when running on battery

Categories

(Core :: Graphics, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: smaug, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: power, Whiteboard: gfx-noted)

VSync drives many things in child processes. We'd get longer idle times, run layout flushes less frequently, would get better ui event coalescing and what not if vsync was less frequent.
It might be better if we lowered only the child process vsync rate, not other processes.
It would be a useful experiment, and I'd even like to toy with lowering the frame rate of the compositor if battery is low (as a separate experiment).

Do you know if we have a way in gecko to know whether we are running low on power (or even whether we are on battery)?
Priority: -- → P3
Whiteboard: gfx-noted
/cc'ing Gijs who might be interested in this as part of the browser adjustment work he's researching.
My main concern here is scrolling responsiveness: If we only composite at 30fps, scrolling will be sluggish. It would be much better if we could somehow dial down our main thread refresh tick frame rate, and maybe our OMTA animation sampling frame rate, without locking the compositing frame rate and affecting scrolling.
Keywords: power
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.