Windows 10 gave Win32 apps including Chrome access to a 'segment heap' API to allow apps to reduce memory usage, but as Techdows spotted, Chromium engineers have decided for now to turn off the feature by default in Chrome 85 after discovering it has a negative impact on CPU usage. Chrome 85 should reach stable status in August...
The CPU issue was discovered by an Intel engineer who found that when Chrome used segment heap, it led to significant performance regression in benchmarks on a PC with an Intel Core i9-9900K processor...
Microsoft has defended the trade-off between memory and CPU but conceded it can be implemented better to reduce the impact on CPU performance. "It is common practice to trade one resource for another. More often it's increased memory usage for reduced CPU usage. In this case it's increased CPU usage for dramatically reduced memory usage, or more accurately commit," wrote a Microsoft employee... "In the short term this is a good trade-off of one resource for another as memory/commit usage is a significant pain point for browser users," argued the Microsoft employee....
However, Chromium developers want to see more evidence about the possible impact of Chrome using segment heap... "The CPU cost (10% slowdown on Speedometer 2.0, 13% increase in CPU/power consumption) is too great for us to keep."
From Slashdot via zdnet
The CPU issue was discovered by an Intel engineer who found that when Chrome used segment heap, it led to significant performance regression in benchmarks on a PC with an Intel Core i9-9900K processor...
Microsoft has defended the trade-off between memory and CPU but conceded it can be implemented better to reduce the impact on CPU performance. "It is common practice to trade one resource for another. More often it's increased memory usage for reduced CPU usage. In this case it's increased CPU usage for dramatically reduced memory usage, or more accurately commit," wrote a Microsoft employee... "In the short term this is a good trade-off of one resource for another as memory/commit usage is a significant pain point for browser users," argued the Microsoft employee....
However, Chromium developers want to see more evidence about the possible impact of Chrome using segment heap... "The CPU cost (10% slowdown on Speedometer 2.0, 13% increase in CPU/power consumption) is too great for us to keep."
From Slashdot via zdnet