Author: Chromium Blog
Source
From the beginning, we designed Chrome to be efficient. Being efficient is not just about loading pages as fast as possible, it’s also about doing it with the least amount of resources possible. Today’s The Fast and the Curious post explores how we improved Chrome to maximize battery life on Mac, so you can enjoy browsing and watching videos longer than ever before.
With the latest release of Chrome, we’ve made it possible to do more on your MacBook on a single charge thanks to a ton of optimizations under the hood. In our testing, we found that you can browse for 17 hours or watch YouTube for 18 hours on a MacBook Pro (13″, M2, 2022). And with Chrome’s Energy Saver mode enabled, you can browse an additional 30 minutes on battery(1). Of course, we care deeply about all our users, not just those with the latest hardware. That’s why you’ll also see performance gains on older models as well.
Here’s a closer look at some of the changes we made:
Fine tuning iframes
We realized that many iframes live just a few seconds. As a result, we fine-tuned the garbage collection and memory compression heuristics for recently created iframes. This results in less energy consumed to reduce short-term memory usage (without impact on long-term memory usage).
Tweaking timers
Javascript timers were introduced at the beginning of the Web’s history. Since then, Web developers have access to more efficient APIs to achieve the same (or better!) results. But Javascript timers still drive a large proportion of a Web page’s power consumption. As a result, we tweaked the way they fire in Chrome to let the CPU wake up less often.
Similarly, we identified opportunities to cancel internal timers when they’re no longer needed, reducing the number of times that the CPU is woken up.
Streamlining data structures
We identified data structures in which there were frequent accesses with the same key and optimized their access pattern.
Eliminating unnecessary redraws
We navigated on real-world sites with a bot and identified Document Object Model (DOM) change patterns that don’t affect pixels on the screen. We modified Chrome to detect those early and bypass the unnecessary style, layout, paint, raster and gpu steps. We implemented similar optimizations for changes to the Chrome UI.
There’s always more work to be done. With the open-source benchmark suite, we’ll be able to tap the broader community of devs to help us to improve Chrome’s power consumption in 2023 and beyond.
Posted by François Doray, Software Developer, Chrome
___
1 Testing conducted in February 2023 using Chrome 110.0.5481.100 on a MacBook Pro (13”, M2, 2022 with 8 GB RAM running MacOS Ventura 13.2.1) and measured using our open-source benchmark suite.
