Chrome is without argument, the simplest and by benchmarks one of the fastest web browsers available if not THE fastest. But a recent investigation has revealed that it’s draining your laptop’s battery faster. Yes! you heard it right, Google Chrome drains battery faster.
This is really bad news and bad development on the engineers’ part, who are responsible for the development and shipment of Google Chrome, a browser used by 59.3% of the internet users around the world (Biggest market share). And after this worrisome disclosure, people are now talking about switching to other alternatives. Spending good buck on a laptop so you can go mobile with your work and data only to realize later that your web browser is killing the point, does seem unfair and switching sounds like a good idea.
How is chrome draining your windows laptop’s battery life? Well, it was found that instead of using the windows recommended clock ticks for CPU usage, meaning the interval of time after which the CPU should wake up from sleep to accomplish any tasks assigned, chrome just goes ahead and reduces the interval about 1/16th of that time. To be exact, the recommended Clock tick is set at 15.625 ms while chrome uses clock ticks of 1.ooo ms. What this means is, instead of waking up 64 times per second, chrome wakes up the CPU 1,000 times in a second to see if anything needs attention. The CPU stays awake longer and hence consumes more power which ultimately drains your battery faster.
Small utility lets you check System Clock Resolution.
Microsoft, the defamed makers of the internet explorer, took this opportunity to go ahead and put the numbers in even more perspective by saying this is almost 25% increase in power consumption. Moreover, the system tick rate is global, so if one application tinkers with it, the whole system usage gets affected and everything is using more battery. The average person has never bothered about tick rates because they don’t even know it could cause a problem.
But you shouldn’t just pull out your guns on Chrome yet. System ticks are not always kept at 15.625 ms and even the internet explorer, when heavy processing is required like streaming a video from YouTube, reconfigures it to 1.000 ms just like other applications do when they need to perform CPU usage demanding tasks. The Chrome browser is just doing it the whole time instead of optimizing the configurations.
Macs and Linux users don’t have to worry because their systems work on something called “Tickless timers”. Pointing this out doesn’t solve the problem for Windows users by the way. Also the fact that Internet Explorer and Firefox both do not exhibit this issue makes it worse for Google.
Google is not a bad guy, as we all know, they respond to the people’s calls and they have done the same with this. This issue has been registered as an internal bug and the necessary attention is being given to the resolution.