Firefox said it would have been said to have been enabled for many times by default (internally called e10s-multi project). According to Firefox developersEric Rahm said, The architecture is scheduled for the next 54 release, then up to four processes can be used to manage Web content, rather than the default is one.
Eric Rahm conducted a memory test for the user's concern about memory usage, and said: "After the previous measurements found that the four content process is the best choice for memory usage and performance. As a follow-up, we would like to run the test again to confirm my conclusion. I used the atsy project to load 30 pages to measure the memory usage of each process generated by each browser during this period. & Rdquo;
The results are as follows:
The browsers involved in the test include IE 11 and Edge 38 on Windows 10, Chrome 59 Beta on all platforms, Firefox Beta 54 on all platforms, and Safari 29 technical preview on MacOS 10.12.4.
You can see, Chrome is still eating large memory, IE 11 in the memory control has done very well Its successor Edge, and Chrome close. Enabled multi-process Firefox in the memory footprint and we do not imagine the high, of course, this is only the developer's own test results, for reference only.
We may wish to share the daily use of the situation, as well as the use of the browser.