Open Bug 1669307 Opened 5 years ago Updated 1 year ago

Investigate relaxing windows timer granularity, especially on battery, to reduce energy use

Categories

(Core :: XPCOM, enhancement)

Product:
Core
Component:
XPCOM
Type:
enhancement

Tracking

()

Project Flags:
Performance Impact low

People

(Reporter: jesup, Unassigned, NeedInfo)

Details

(Keywords: perf:resource-use)

Chrome has recently relaxed windows timer granularity to 8ms (from 1ms): See https://randomascii.wordpress.com/2020/10/04/windows-timer-resolution-the-great-rule-change/ and https://bugs.chromium.org/p/chromium/issues/detail?id=927165 and https://chromium-review.googlesource.com/c/chromium/src/+/2265402 (Chrome changed from 4ms to 8ms). The power curve is exponential.

We should consider raising our timer granularity when on battery power.

Currently we raise it when playing videos, temporarily for throttling network bursts, running the profiler, and momentarily in webrtc code.

NI to padenot to investigate the impact of relaxing granularity for media playback

Flags: needinfo?(padenot)
Whiteboard: [qf] → [qf:p3:resource]
Performance Impact: --- → P3
Keywords: perf:resource-use
Whiteboard: [qf:p3:resource]
You need to log in before you can comment on or make changes to this bug.