Slashdot Mirror


Mozilla Unleashes the Kraken

An anonymous reader writes "Mozilla has released the first version a new browser benchmark called Kraken. Mozilla's Robert Sayre writes on his blog, 'More than Sunspider, V8, and Dromaeo, Kraken focuses on realistic workloads and forward-looking applications. We believe that the benchmarks used in Kraken are better in terms of reflecting realistic workloads for pushing the edge of browser performance forward. These are the things that people are saying are too slow to do with open web technologies today, and we want to have benchmarks that reflect progress against making these near-future apps universally available.' On my somewhat elderly x86_64 Linux system Google Chrome 6.0.472.55 beta completes the Kraken benchmark in 28638.1 milliseconds, Opera 10.62 completes it in 23612.4 milliseconds, and the current Firefox 4 nightly build completes it in 19897.5 milliseconds."

6 of 363 comments (clear)

  1. Obvious... by Firehed · · Score: 2, Interesting

    How about IE performance? Too bad to even mention?

    --
    How are sites slashdotted when nobody reads TFAs?
    1. Re:Obvious... by edgrale · · Score: 5, Interesting

      It's still running.

      Laugh all you want but I have had it running on IE 8 (Windows 7 64 bit) for the past 5 minutes and it is still stuck at the first stage. So I think we have a legitimate reason why Internet Explorer was not included...

      Also got a warning that "A script on this page is causing your web browser to run slowly."...

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  2. Re:I hope that Firefox isn't playing Microsoft's g by Haedrian · · Score: 3, Interesting

    Why don't they just grab the (say) 200 most visited sites on the internet, copy the JavaScript and use that to benchmark instead?

    Simples.

  3. Re:I hope that Firefox isn't playing Microsoft's g by BZ · · Score: 3, Interesting

    Because the amount of time it takes to run the javascript on the top sites is pretty small (which is what the IE team was talking about around IE8's release). Performance on those sites mostly doesn't depend on whether your JS engine is the one in Chrome dev or the one in IE7. I only say "mostly" because I wouldn't be surprised if gmail is in the top 200. ;)

    If you're going to worry specifically about JS performance (which is an assumption; the IE team is still saying that this focus is a mistake and to some extent they're right), you want to be benchmarking things that are gated on JS performance. That means identifying t the things that are slow with current JS engines and that people would like to be doing but can't because of said slowness, whatever those things are, and benchmarking those.

  4. Mozilla releases a Windows botnet by hAckz0r · · Score: 2, Interesting

    Mozilla Unleashes the Kraken https://secure.wikimedia.org/wikipedia/en/wiki/Kraken_botnet. I just wonder if this is somehow a 'Freudian slip', just to remind the world of how vulnerable the competition is?

  5. Re:Javascript by Richard_at_work · · Score: 2, Interesting

    Yes, I have used JS on the server and I wouldn't use it for anything production in place of .Net - the frameworks and language features are just not there to be competitive yet.

    On the server side, fast is not enough. I don't want to be reimplementing functionality I know I can get elsewhere very very cheaply.