Google already admitted that when it comes to preserving battery life, Safari web browser is better, but they are working their way up to make Chrome more efficient for Mac users. Google announced earlier this month to please Mac users, they are making Chrome more battery efficient on Mac. Google has a new feature that can identify the presence of unnecessary Flash content on a web page and then shuts it down.
Peter Kasting a Senior Chrome engineer, posted on Google+, "One of the big complaints about Chrome currently is that it's a battery hog, especially on Mac where Safari seems to do better."
According to BetaNews, Google knows that Chrome makes the batteries run down faster, and they are vigorously working to optimize Chrome on OS X, and solve the browser's power efficient problems on Mac.
Peter Kasting stated that their recent discovery about Chrome's efficiency is just the beginning, and the Chrome team is piling up more plans for the ongoing improvements of the browser's performance.
Engineer Peter Kasting said, "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."
A Google+ user posted, that he had heard complaints about the excessive RAM usage, another Google+ user stated that it is much better to have an optimized RAM, where he got only 2GB RAM for his laptop - and he suffered to deal with the issue of preserving battery life.
During a Reddit AMA last month, Google is much committed to address the users' complaints, and that coming up with a solution is on their priority lists. Chrome is being improved by Google in it's start-up speed and they are proactively taking control of memory bloat and memory leaks.
Kasting said about Chrome will reduce the CPU usage, "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 percent CPU usage vs. Safari's 120 wakes over 30s and 0.1 percent CPU usage. Now: 66 percent reduction in both timer firings and CPU use. Chrome is now incurring ~120 wakes over 30s and 0.1 percent CPU use, on par with Safari".
