"The CPU cost (10 percent slowdown on Speedometer 2.0, 13 percent increase in CPU/power consumption) is too great for us to keep. If prompted, you'll have to enter your Mac's password before continuing. Click and drag the Chrome icon onto the Applications folder icon. Google engineer Bruce Dawson found that SegmentHeap was able to reduce Chrome's memory usage by 30 percent - but the CPU trade-off was too great.Īfter weeks of testing Dawson explained: "The plan is to disable this for M85 (thus giving us another telemetry datapoint) and reconsider in the future. It will be in your Mac's default downloads location (e.g., the Downloads folder). The test for the SegmentHeap feature, which was aimed at reducing Chrome gobbling up RAM, was stopped after Google discovered it had the knock-on effect of increasing CPU usage. The latest Google Chrome news comes after last month Google stopped testing a Windows 10 memory optimisation that had been developed by Microsoft. Watch this space for more on that work when it is broadly available!" We see improvements not only in loading speed but also battery and memory savings.
It should be landing on the Canary release. Christoff also said that Google will be adding a new feature known as Tab Throttling to the beta version of Chrome 86 in September.ĭescribing this other new addition, Christoff wrote: "We know you need a lot of tabs to do your work, and with tab throttling - now rolling out on Beta channel - Chrome will give more resources to the tabs you’re using by taking them back from tabs that have been in the background for a long time. Google recently changed Chromes release cycle from its usual six weeks to four, which means Chrome 100 has been creeping up on us a lot faster lately.
0 kommentar(er)
