婆罗门
精华
|
战斗力 鹅
|
回帖 0
注册时间 2009-8-26
|
有什么不该信的,以前就那样,也就5x这几个大版本靠Opera贡献的代码和它自己的升级侧重点,进步明显;同时FF那边有比较严重的缓存泄漏问题,也是到4x之后慢慢修好这锅。Chrome有很多长处,但你强行甩这锅就不清真了。
随便搜一下,字眼“firefox chrome ram”:
http://www.itpro.co.uk/web-browsers/24796/which-is-the-best-browser-chrome-vs-firefox-vs-internet-explorer-5/page/0/1
Which is the best browser?: Chrome vs Firefox vs Internet Explorer 2017 Apr 7
Memory consumption
To test this, with measured the amount of memory used by each browser during a medium session: one window with a Facebook page, a YouTube video, a BBC News article, the Microsoft Outlook web app and the IT Pro homepage open in separate tabs.
Looking at the Windows task manager, it’s easy to assume that Chrome is a resource-hungry beast, as the browser will often list multiple simultaneous processes. However, this can be deceptive as the chrome files each separate tab, extension and plug-in as a separate process.
This allows it to isolate any potential crashes or hiccups caused by specific processes while the rest of the browser remains operational. Add the total memory usage up, and it’s really not as bad as it looks.
That doesn’t mean it’s good, however. Overall, it’s still the most memory-hungry browser we tested, beating IE by a hair’s breadth. Firefox was considerably less demanding than either, tying up an average of 412,000KB compared to the almost 600,000kb eaten up by Chrome and IE.
http://www.makeuseof.com/tag/chrome-vs-firefox-in-2016-which-browser-is-right-for-you/
Chrome vs. Firefox in 2016: Which Browser Is Right For You?
Light on Resource Usage
Chrome has a nasty reputation for being a resource hog. It eats up RAM, it spikes in CPU usage, and as a result, it kills battery life on portable devices. To be fair, Firefox is no saint either when it comes to resource usage, but compared to Chrome it’s definitely more mindful and less greedy.
http://neurogadget.net/2016/11/01/google-chrome-vs-mozilla-firefox-ram-consumption/44781
Google Chrome vs Mozilla Firefox – RAM Consumption November 1, 2016
Basically, Chrome uses considerably more memory compared to Firefox, when many tabs are currently open. This is said to be in connection to its implementation of the separate-process-per-tab.
For Firefox, it takes longer for releasing memory despite the fact that the tabs have been closed already. In fact, in older versions of Firefox, it consumes more and more memory quantity without releasing it. As others would say, it is the memory leak of Firefox. However, Mozilla suggests that it was actually due to issues of memory fragmentation. Thus, it exhibits many of the resource and performance consumption symptoms that may look like a memory leak.
In Chrome’s favor, however, opening and closing tabs may be proven beneficial due to its instant release of memory upon closing the tabs. So, overall, Chrome doesn’t consume more memory.
|
|