Jul 20 2006

Fundamental flaws in browser showdowns

ExtremeTech is running a story comparing Opera 9.0, IE 7.0b3, and Firefox 2.0b1. While the table they include regarding features is just fine and dandy, they spend significant amounts of time measuring performance. Sure, that’s fair: compare a beta’s performance with that of a final product.

Also, something strikes me as fundamentally wrong with data when a freshly-loaded Opera with no loaded tabs requires 53MB of system memory, and the same Opera with a predetermined set of loaded tabs requires… 52MB of system memory. Anyone else smell something fishy?

5 Responses to “Fundamental flaws in browser showdowns”

  1. Rustyon 20 Jul 2006 at 7:26 am

    No idea whether it’s fishy or just plain wrong, but my Opera starts up at 18MB and with 6 tabs (not the ones they used, but still) at 40-oddMB.

  2. Heliologueon 20 Jul 2006 at 8:26 am

    No doubt that it’s a fine, fine product.

  3. Rustyon 20 Jul 2006 at 9:45 am

    Oh I don’t doubt that you were doubting it, I just thought I’d supply my own figures instead. I had planned on making an observation or two on IE7 in that comment as well, but I had to go to the hospital appointment from which I’ve just returned and about which I’m just about to blog before I get some food and go to work. So just imagine that I said something relevant here (or there, as it were).

  4. Rustyon 20 Jul 2006 at 9:49 am

    Weren’t.

    Or just change the first 9 words to something that isn’t stupidly awkward.

  5. robon 20 Jul 2006 at 2:18 pm

    Psst, reserved memory is not “memory usage”. Firefox often reserves 100 MB of RAM on my machine, but hands it over to other applications that need it without a fuss. Firefox isn’t “using” 100MB of memory and Opera is not “using” 50MB of memory.

Trackback URI Comments RSS

Leave a Reply