Comments on: Chrome vs IE Javascript Engine Performance Comparison

By: Custom Research Papers

Custom Research Papers — Sat, 30 Jan 2010 05:18:10 +0000

Hi,
This is really such a great idea; you have done a great gob

By: technokitty

technokitty — Thu, 14 Jan 2010 19:11:02 +0000

Oh cmon..I find the options n preferences menu in Chrome completely rubbish…I mean they hardly give you any options with just the three tabs…Opera gives you 5, Firefox and IE give you 7 or 8…and its not like the Chrome developers have been working overtime to give you sleek UI’s, … just try setting up a proxy to connect to a network in Chrome and it simply switches to the IE settings menu…that’s original!

By: Alfred

Alfred — Mon, 04 Jan 2010 20:59:15 +0000

I think one of the most advertised strong point in Chrome is the script engine supposedly delivering far better performance than any other browser.

This may be the case in the pages written specifically for Chrome but it is really not true on the everyday pages you can find on the Internet.

On the contrary, Chrome may prove to be the slowest. I had noticed that when developing my site that uses the Image Flow js component from Finn Rudolph. Have a look at http://faltiska.net/en. Use your mouse scroll on the visual navigator.

Do that in Firefox, Opera, IE and Chrome. Chrome is really bad. IE is annoying because of the tearing but the movement is more fluent. Firefox and Opera are near perfect.

So, what is Google bragging about?

By: Oliver Mezquita

Oliver Mezquita — Thu, 05 Nov 2009 14:59:24 +0000

Yeap, Google beats all of its competitors by far. And IE just plain sucks. That’s it. There’s no more to it!

By: Slimshadym23

Slimshadym23 — Thu, 06 Aug 2009 04:44:30 +0000

It’s like a controversial thing when i ran the test.
Mozilla, ran successfully and gave me some value above 100. In IE6 it gave me that script warning whether you wanna stop the script or continue.. after i allowed it to continue, it became irresponsive and started hogging the memory ( i saw it in task manager it was having some over 400K). it was on win XP, 2MB ram, intel core 2 1.7GHz.

Then at home Mozilla fairly ran for sometime and started giving me warning message like whether you wanna stop the script or you wanna continue running the script. Then after hitting continue it ate memory upto 200K and completed the test. and IE 7 behaved the same way like IE6. It was on Win XP, 1GB ram, intel pentium 4.3GHZ.

I was wondering, whether in chrome is this really a radical improvement or the V8 benchmark is tweaked to perform good exclusively for chrome.

Again I am gonna run this test in IE8 and chrome. And let me post my observation.

-Maran.

By: Snow user

Snow user — Fri, 17 Jul 2009 04:56:34 +0000

Well… Safari on Snow pulls a Score of 2268, running a stock iMac 2.8GHz Intel Core 2 Duo with 4 GB of RAM

Score: 2268
Richards: 3876
DeltaBlue: 2221
Crypto: 3034
RayTrace: 2935
EarleyBoyer: 2855
RegExp: 1020
Splay: 1385

By: admin

admin — Fri, 20 Feb 2009 20:02:30 +0000

I am wondering what javascript framework it was as you mentioned above?

By: Anthony Alexander

Anthony Alexander — Fri, 20 Feb 2009 18:05:00 +0000

The numbers are misleading.

My Javascript framework includes a fps counter. IE 7 runs about 75% slower than IE6, I actually uninstalled it when i saw those numbers. IE 8 goe sback up to about 30.

Safari, Opera and Firefox hover around 80-90FPS but Firefox jumps to 110+ every now and then.

I was getting about 550+ with Chrome Beta, then it went down to 300 close to realease, right now its in the low 200s(220-250).

Now when it comes to actually rendering the page, IE 6 was the smoothest followed by Opera. Firefox was plagued with artifacting issues and a generally buggy rendering setup. Safari followed up then Chrome last. The numbers also drop most dramatically for Chrome under load.

Right now Safari has the best rendering, followed by Chrome, Opera, Firefox(when it finally LOADS) and then IE8.