Slashdot Mirror


Google Frame Benchmarks 9x Faster than IE8

ChiefMonkeyGrinder writes "Early tests with Google's Chrome Frame found IE8 runs 9.6 times faster than usual. The testers ran the SunSpider JavaScript benchmark suite." The other question is what is the performance hit of using the Frame plug-in instead of running the browser natively.

5 of 152 comments (clear)

  1. FFS read the articles you post! by hattig · · Score: 3, Informative

    The other question is what is the performance hit of using the frame plug-in instead of running the browser natively.

    FTFA: "Notably, IE8's SunSpider scores with Chrome Frame running equaled Google's Chrome browser"

  2. Re:Defeats the purpose of IE by Anonymous Coward · · Score: 4, Informative

    you have to add meta tag to make chrome frame work, otherwise it uses slow ie engine

  3. Re:So just for giggles... by rliden · · Score: 3, Informative

    IE8 still fails the Acid3 test even with Google Chrome Frame installed. I was curious and tested it out. Chrome Frame doesn't take over full rendering from IE8 unless the site includes a meta tag to use the Chrome Frame. Here is a link to the Chrome Frame page [code.google.com] (chocked full of good info).

    --
    Don't think of it as a flame, more like an argument that does 3d6 fire damage.
  4. Re:Defeats the purpose of IE by ControlFreal · · Score: 3, Informative

    So now with Chrome infecting my IE, I have no way to access vital corporate apps.

    But you have: The Chrome-frame mode is activated only if one either prefixes URLs with cf: (which your corp. apps will not do), or if one includes a <meta http-equiv="X-UA-Compatible" content="chrome=1"> header in the HTML (or HTTP), which your corp. apps will not do either.

    Only websites specifically designed to use the Chrome frame could force IE into Chrome-frame mode.

    --
    Support a Europe-related section on Slashdot!
  5. Re:So just for giggles... by emurphy42 · · Score: 3, Informative

    But the rendering is off a bit in the upper right corner. I just tested native Chrome - 3.0.195.21, I haven't updated it in a good while - and it has the same problem.