One of the big complaints about Chrome currently is that it's a battery hog, especially on Mac where Safari seems to do better.
The team has been working on addressing this; here are some cases that have recently been improved on trunk:http://crbug.com/460102Before:
Renderers for background tabs had the same priority as for foreground tabs.Now:
Renderers for background tabs get a lower priority, reducing idle wakeups on various perf test, in some cases by significant amounts (e.g. 50% on one test).http://crbug.com/485371Before:
On a Google search results page, using Safari's user agent to get the same content that Safari would, Chrome incurs ~390 wakes over 30s and 0.3% CPU usage vs. Safari’s 120 wakes over 30s and 0.1% CPU usage.Now:
66% reduction in both timer firings and CPU use. Chrome is now incurring ~120 wakes over 30s and 0.1% CPU use, on par with Safari.http://crbug.com/489936Before:
, Chromium incurs ~1010 wakeups over 30s vs. Safari's ~490 wakes.Now:
~30% reduction in timer firings. Chrome is now incurring ~721 wakeups over 30s.http://crbug.com/493350Before:
, Chromium incurs 768 wakups over 30s and consumes ~0.7% CPU vs. Safari's 312 wakes over 30s and ~0.1% CPU.Now:
~59% reduction in timer firings and ~70% reduction in CPU use. Chrome is now incurring ~316 wakeups over 30s, and 0.2% CPU use, on par with Safari at 312 wakes, and 0.1% CPU use.
The Chrome team has no intention of sitting idly by (pun intended) when our users are suffering. You should expect us to continually improve in this area.