MSI has several lines of gaming notebooks catering to different types of users. At the high-end is the GT series that supports the fastest mobile CPUs and GPUs while the GE series caters more towards the cost-conscious buyers. Somewhere in the middl…
MSI has several lines of gaming notebooks catering to different types of users. At the high-end is the GT series that supports the fastest mobile CPUs and GPUs while the GE series caters more towards the cost-conscious buyers. Somewhere in the middl…
Last week we posted our Browser Face-Off: Battery Life Explored 2014, where the battery run down times of Firefox 31, IE11 Desktop, IE11 Modern, Chrome 36, and Chrome 37 beta were tested on Windows. We used GUI automation to open browsers, tabs, and visit websites to simulate a real user in a light reading pattern. The article answered a lot of questions about popular browser battery life on Windows, but it raised additional questions as well.
Chrome 36 tested with the best battery life, but was the only browser that did not render correctly at 3200×1800 due to lack of HiDPI support. In the Chrome 37 beta, HiDPI support improved rendering but also took a 25% dive in battery life tying it for last place. However, the Chrome 37 beta includes more changes than just HiDPI support (along with some debugging code), so was the battery life penalty from the now-native 3200×1800 rendering or was it something else? After a few more days of testing at 1600×900 with 100% DPI scaling, we can narrow in on an answer.
When both Chrome 36 and Chrome 37 beta natively render at 1600×900 there is less than 3% difference in battery life. Two tests of each browser were performed and the results averaged. The variation between runs was only 1%. Looking at our previous numbers of Chome 36 and 37 beta on the HiDPI setting of 3200×1800 and 200% scaling, the situation is entirely different.
I’ve added an asterisk here (and clarified the same text on the original article) to indicate Chrome 36 isn’t actually rendering at 3200×1800, but rather at 1600×900 and relying on Windows DPI Virtualization to scale up to 3200×1800.
Looking at the numbers, there’s some good news and some bad news. The good news is that Chrome 37’s new features likely won’t hurt the battery life of current users. If you are using Chrome now, you are probably not using a HiDPI display due to the existing blurry rendering. For these users, the pending Chrome 37 upgrade has no significant impact on battery life. The bad news is that if you have been avoiding Chrome due to its HiDPI rending issues, Chrome 37 resolves those issues but also appears to provide worse battery efficiency compared to Internet Explorer. On our XPS 15 that equated to about an hour less of mobility.
Given that this is the first version of Chrome to properly support HiDPI, it’s entirely possible – even likely – that there are many opportunities to further optimize the algorithms and hopefully return battery life at least close to Chome 36 levels. A slight dip in battery life is expected as it takes more work to render a 3200×1800 image compared to a 1600×900 image, but a 20% drop seems rather extreme. We’ll have to see what future updates bring, but hopefully by noting the discrepancy it will encourage developers to better tune performance.
Last week we posted our Browser Face-Off: Battery Life Explored 2014, where the battery run down times of Firefox 31, IE11 Desktop, IE11 Modern, Chrome 36, and Chrome 37 beta were tested on Windows. We used GUI automation to open browsers, tabs, and visit websites to simulate a real user in a light reading pattern. The article answered a lot of questions about popular browser battery life on Windows, but it raised additional questions as well.
Chrome 36 tested with the best battery life, but was the only browser that did not render correctly at 3200×1800 due to lack of HiDPI support. In the Chrome 37 beta, HiDPI support improved rendering but also took a 25% dive in battery life tying it for last place. However, the Chrome 37 beta includes more changes than just HiDPI support (along with some debugging code), so was the battery life penalty from the now-native 3200×1800 rendering or was it something else? After a few more days of testing at 1600×900 with 100% DPI scaling, we can narrow in on an answer.
When both Chrome 36 and Chrome 37 beta natively render at 1600×900 there is less than 3% difference in battery life. Two tests of each browser were performed and the results averaged. The variation between runs was only 1%. Looking at our previous numbers of Chome 36 and 37 beta on the HiDPI setting of 3200×1800 and 200% scaling, the situation is entirely different.
I’ve added an asterisk here (and clarified the same text on the original article) to indicate Chrome 36 isn’t actually rendering at 3200×1800, but rather at 1600×900 and relying on Windows DPI Virtualization to scale up to 3200×1800.
Looking at the numbers, there’s some good news and some bad news. The good news is that Chrome 37’s new features likely won’t hurt the battery life of current users. If you are using Chrome now, you are probably not using a HiDPI display due to the existing blurry rendering. For these users, the pending Chrome 37 upgrade has no significant impact on battery life. The bad news is that if you have been avoiding Chrome due to its HiDPI rending issues, Chrome 37 resolves those issues but also appears to provide worse battery efficiency compared to Internet Explorer. On our XPS 15 that equated to about an hour less of mobility.
Given that this is the first version of Chrome to properly support HiDPI, it’s entirely possible – even likely – that there are many opportunities to further optimize the algorithms and hopefully return battery life at least close to Chome 36 levels. A slight dip in battery life is expected as it takes more work to render a 3200×1800 image compared to a 1600×900 image, but a 20% drop seems rather extreme. We’ll have to see what future updates bring, but hopefully by noting the discrepancy it will encourage developers to better tune performance.
It has been five years since we did a benchmark of the various web browsers and their effect on battery life, and a lot has changed. Our testing then included Opera 9 & 10, Chrome 2, Firefox 3.5.2, Safari 4, and IE8. Just looking at those version numbers is nostalgic. Not only have the browsers gone through many revisions since then, but computer hardware and the Windows operating system are very different. While there has been a lot of talk, there hasn’t been a lot of data comparing browser battery usage. Today we’re going to put the latest browsers to the test and deliver some concrete numbers.