Slashdot Mirror


Memory Usage of Chrome, Firefox 3.5, et al.

An anonymous reader writes "This experiment graphs the memory usage of Chrome and Firefox 3.5 (along with Safari and Opera) over a series of 150 Web page loads using an automated script. Firefox 3.5 shows the lowest memory usage in all categories, including average memory usage, maximum memory usage, and final memory usage. Chrome uses over 1 GB of memory due to its process architecture. Safari 4 and Opera show memory usage degradation over time, while Chrome and Firefox 3.5 are more reliable in freeing memory to the OS." IE 8 was not included "because the author could not find a way to prevent it from opening a new window on each invocation of the command."

5 of 505 comments (clear)

  1. Re:It doesn't matter by Ethanol-fueled · · Score: 5, Insightful

    Something like "it doesn't show weird ass icons and bars when Slashdot decides to change CSS" is probably much more important.

    I'm no web developer, but I don't quite believe that those artifacts are Firefox's fault. Why the staff would make broken changes on a live site is anybody's guess. Those artifacts are relatively minor annoyances but they won't serve the people who are considering switching to Linux and getting into open source only to discover that the primary forum for Linux nerds is every bit as broken as the Linux their Microsoft-loving buddies describe.

  2. Moving targets by mcrbids · · Score: 5, Insightful

    There's no answer that's always right. If memory usage was paramount, we'd all have browsers that used 1 MB of RAM and took 10 minutes to render a page, with another 2 minutes to scroll down a page.

    But RAM is cheap and developers have to make compromises based on the real-world that they have to compete in. I can get a gig of RAM for about the cost of a burger lunch with my wife.

    Do I really care about memory usage? Only to the extent that it's 'good enough' on my slowest computer - a dual-core Mac Mini with 512MB.

    FF3 is plenty good enough for me to thoroughly enjoy an episode of 'Burn Notice' on Hulu just now on that very computer.

    Sorry you are having probs with memory usage on your (ancient?) computer. Perhaps you should consider forgoing a burger lunch this week?

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
  3. Why not testing IE 8? by VincenzoRomano · · Score: 5, Insightful

    The author says he didn't included IE 8 because there was no way to start it without opening a new window for every invocation!
    I would have preferred to have it included despite this "big drawback" and have this thing explained in a note.
    A partially meaningful test (upper limit?) is always better than no test at all!
    I fear that this omission is to "protect" bad performances even in comparison of a browser by a company which seems to be in deep competition with Microsoft.

    --
    Maybe Computers will never be as intelligent as Humans.
    For sure they won't ever become so stupid. [VR-1988]
  4. Re:It doesn't matter by kripkenstein · · Score: 5, Insightful

    Unless you are talking about a system with severely limited memory, memory usage is probably not the right criteria for deciding which browser to use.

    Chrome used over 1 GB in this test. Safari and Opera passed the 500 MB mark. That is an issue for far more machines than 'systems with severely limited memory'.

  5. Re:Finally... by Seumas · · Score: 5, Insightful

    Too bad it won't stop all the "what memory problem?" trolls.

    Remember how 3.0 was touted to solve all the memory problems? I still get 1.5gb of usage *regularly* on multiple platforms with 3.0.11 without any installed extensions after a few hours. In fact, I'm on Firefox 3.0.11 on OSX 10.5.7 right now and it's at 1.3gb. You can tell when it's being a memory hog again, because videos won't play without stopping and stuttering and pages take longer to load and switching tabs feels glacial.

    So, considering 3.0 originally was supposed to solve everything, I think I'll not hold my breath on 3.5. Especially for a problem that continues to happen across platforms.