For anyone ever working on a metered internet connection, they would notice that Google Chrome tends to use a significant amount of their data allowance through simple web browsing. The reason behind this is that Google Chrome operates on a smart inference basis which it uses to download more data than is currently in use in anticipation of your next click. Google Chrome also does not limit or optimize its webpages and downloads all the content on a site for the most clear cut and complete preview. For those of us that want the most high-end display of a website, that’s great news, but for most who are working on a limited data plan for the month, Google Chromes usage can come across as rather alarming.
Previously, all tabs ever loaded on Google Chrome would reload when the application was relaunched in anticipation of you wanting to visit a previous tab. In addition to this, while in use (and to some extent when not in use), background tabs would continue sending and receiving data to keep them updated for your next viewing. This consumed an unbelievable amount of internet data as well as battery power as this process demanded a lot of the processor’s attention and capacity. This has been brought to Google’s attention many times and its task force has been working on a solution that maintains Chrome’s flawless interface and servicing whilst optimizing data and power usage.
Google has come forward with a solution that limits the activity of its Chrome tabs. The company has resolved to terminate the sending and receiving activity of any tabs after five minutes of inactivity to improve the browser’s performance. Experimenting with this solution has shown that Chrome is in fact able to provide better performance when it only has one or two tabs to focus on reloading as opposed to the 50 some people never close. In addition to this, after the five minutes of inactivity marker, background data and power usage of the application is minimized as its activity is terminated. In a thorough report published by Google, we can see that through multiple tests conducted on this new mechanism, the company observed significant improvement in data usage, battery usage, and overall device performance. Google will use its success and regression metrics to continue to gauge this process. The RendererScheduler.TaskDurationPerQueueType2.Background.AfterFifthMinute Code has been observed since April. Google has reported 5.54% decrease in background downstream cellular, 1.12% decrease in foreground downstream cellular and 1.78% increase in background upstream cellular as of the 6th of June, 2018, and the code was then declared stable.