Google Chrome has a problem with laptops. In addition to the occasional performance details, Mountain View browser demand a sacrifice in the form of battery . Even Microsoft placed pressure on this point to promote Edge and the developers have worked for a long time to correct the situation. After what was his formal announcement in September of the year passed, 57 of Google Chrome version now includes a ‘throttling’ for the tabs in the background, in such a way that not to claim more than 1 percent of the CPU.
the picture of modern browsers is regrettable . At the moment I am running an instance of Firefox, and another of Chrome. The Mozilla browser has decided to devour a total of 977 megabytes of RAM for three tabs and two extensions which flatly refuses to return. On the other side, Chrome still suffers existential crisis whenever I do a bit of scrolling on portals like Facebook. The result is a sort of break dance-toxic which uses 50 percent of a processor with four cores, and command there in the section flags or extension in the store that will help with this. Another very serious problem suffered by Google browser is laptops battery consumption. No matter the model or operating system, Chrome is responsible for squeeze batteries as if they were oranges.
the engineers discovered that many pages consume a lot of CPU cycles even when found on a tab in the background . With the arrival of Chrome 57 that behavior will change. The key is a new system of ‘throttling’ based on a budget (medido en segundos) each tab in the background is subjected to that after a 10 seconds pass. That budget is regenerated (con un factor de 0.01 segundos «por» segundo) but the tab background can only access called “wall time” CPU (wall time es el tiempo real que necesita un proceso para iniciar_se y completar su tarea) has provided not exhausted its budget. In other words, it is estimated that the average intake for a tab in the background will be of 1 percent of the CPU.
the main exceptions to the throttling are tabs that reproduce audio (ya que se las considera en primer plano automáticamente) and those that maintain connections in real-time through WebRTC or WebSockets. The Chromium team reported a reduction of ‘tabs occupied» of 25 per cent, and in certain places, the decline in the use of the CPU can get to 75 percent. Of course, what we need now are much stronger measurements by the users, who must be satisfied if this translates into longer battery life. But the story doesn’t end there. Towards the year 2018, will be sought total suspension of the tabs in the background.
let your vote
Total votes: 0
Upvotes percentage: 0.000000%
Downvotes percentage: 0.000000%