Google has been trying to reduce the memory usage of Chrome on Windows 10, and Chrome 87 has recently undergone performance upgrades.
Unfortunately, Chrome still eats up a lot of RAM, but Google now claims to be making another very useful change that should reduce memory usage and hopes to end its reputation as a RAM-consuming browser.
Chrome engineers are studying "PartitionAlloc FastMalloc" to make the worst-case active memory usage of certain processes less than 10%. In other words, Google will do better in RAM management and caching to improve the overall performance of the browser.
Google originally planned to use Windows 10's new feature "SegmentHeap", which is a modern heap implementation with improved memory to reduce the overall RAM usage of the application.
Microsoft claims that after using Segment Heap, it found that the memory usage of Chromium-based Edge has been significantly reduced by 27%, and Google has also confirmed that it is willing to adopt it in Chrome.
It now appears that Google has completely abandoned the "SegmentHeap" feature because Microsoft cannot provide "control over heap types." Google said that if you cannot control the heap type in Windows 10, you cannot enable segmented heaps for only certain processes or only certain heaps or both.
Segment Heap also caused "performance degradation" in a CPU-intensive process, and Google abandoned the project.
As mentioned above, Google is now planning to use a new function called PartitionAlloc FastMalloc instead of Segment heap.
This function is basically a memory allocator, which can improve the security and performance of the browser at the same time.
Google will improve browser caching by enabling dedicated partitions. After enabling PartitionAlloc, the number of operations in Chrome will be optimized, and the allocation of resources will also be designed to be very fast.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-