Status: Untriaged Owner: ---- CC: [email protected], [email protected], [email protected], [email protected], maruelatchromium Labels: Type-Feature Pri-3 OS-Windows Area-BrowserBackend Size-Medium Performance BatteryUsage
New issue 21758 by maruelatchromium: Explore SetWaitableTimerEx) as a way to save battery life http://code.google.com/p/chromium/issues/detail?id=21758 We use SetTimer() and WM_TIMER on Windows. See MessagePumpForUI::ScheduleDelayedWork() in http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_win.cc?view=markup Windows 7 supports SetWaitableTimerEx() to add a 'TolerableDelay' (fuzz factor) to the timer fire schedule. That would probably help battery usage by waking up the processor less often and doing more at each wake up. [Win7 MS folks where positive that it does help battery life.] Contrary to SetTimer(), SetWaitableTimerEx() uses a kernel handle and may optionally fire an APC function so it may be problematic to implement. Also, it is fairly possible that WM_TIMER is already so imprecise that using SetWaitableTimerEx() doesn't help. The only way to know for sure is to do a full implementation and do a test run on a win7 laptop to see if it gives real advantage, thus putting it P3. Note: Most javascript assumes 15 ms fuzz anyway so I think it'd be fine to start with 15 ms for javascript events, maybe everything (?) as a test. [Something similar probably be implemented on linux] -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
