![]() ![]() Your mileage will probably vary depending on your browsing habits and how big your pool of RAM is, though. In some brief testing, Firefox 54 does indeed feel a little quicker than before and consumes less memory than Chrome for the same set of tabs. By default Google Chrome starts a new process for every tab, which is one of the reasons it's such a memory hog. Upon being launched, the Firefox web browser internally spawns one privileged process (also known as the parent process) which then launches and coordinates activities of multiple (web) content processes the parent process is the most privileged one, as it is allowed to perform any action that the end-user can. ![]() ![]() If you want to be more (or less) aggressive, you can visit about:config and tweak. Apparently that's the sweet spot between using too much RAM while still taking full advantage of multi-core CPUs. Mozilla says it has worked hard to avoid increased memory consumption, but as a result you only get four content processes by default. The trade-off with multiple processes, though, is memory overhead, because each process contains an instance of the browser's rendering engine. Electrolysis is also a prerequisite for full security sandboxing in Firefox, which is currently only available for a few media-decoding plug-ins such as Flash. In theory, moving to multiple content processes will improve stability and performance (one bad tab won't slow down the rest of your computer). Mozilla is calling Firefox 54 "the best Firefox ever," and it's probably not wrong (though Firefox 3.5 was pretty good, in my opinion). Firefox has finally been outfitted with simultaneous multiple content processes, a UI process, and a GPU acceleration process-eight years after the project, codenamed Electrolysis (E10S), began.
0 Comments
Leave a Reply. |