A complaint I've had with Flash lately is its lack of 64-bit support for Windows. This forces us to run 32-bit browsers on our 64-bit machines if we intend on having Flash support while browsing. My initial thought was that we're missing out on a very nice performance boost because of this. I then questioned just how sure I really was that this performance boost really existed. Thus, I decided to do some really simple testing between some 32 and 64 bit browsers just to see what happens. The results were, interesting, though not necessarily conclusive of much.
The plan is simple. Run a small JS script that will calculate all prime numbers from 1 to 10,000 and record the time taken for the operation. The end code uses a modified algorithm that I stole from the Web Workers Wikipedia page.
Complete browser version list for test:
IE8 8.0.7600.16385 (32 and 64 bit)
IE9 Platform Preview 1.9.7766.6000
Chrome 5.0.375.55 beta
Chromium 6.0.420.0 (48547)
Firefox-32bit 3.6.3
Unofficial Firefox Namoroka/3.6.3 (64 bit) from http://wiki.mozilla-x86-64.com/Firefox:Download
Firefox-32-3.7a5pre Nightly Built on 19-May-2010
Times in ms for 5000:
Times in ms for 10000:
Note I did tell FF to stop dialog'ing about the script taking a while so these oddly high times don't include me clicking the No button for the warning. Thus, I really have no explanation for the obscure duration for FF 32 and 64 to calculate under the 10000 limit.
IE8 also beats Firefox in both tests by considerable margins. Something I find to be rather strange as Firefox has native code compilation for Javascript whereas IE8 does not.
Also of note, in the 5000 limit, IE8-64 actually takes longer than IE8-32. Elsewhere the 64 bit browser out-performed its 32-bit brother but only marginally. Keep in mind, this is a pure mathematical JS test. A more robust test would probably include things like heavy DOM manipulation and HTML tree searching. So again, interesting results but nothing too conclusive regarding 64-bit browsers being extra powerful.
Some graphs:



The plan is simple. Run a small JS script that will calculate all prime numbers from 1 to 10,000 and record the time taken for the operation. The end code uses a modified algorithm that I stole from the Web Workers Wikipedia page.
var n = 1; var holder = document.getElementById('holder'); var startTime = (new Date).valueOf(); search: while (n < 10000) { n++; var nSqrt = Math.sqrt(n); for (var i = 2; i <= nSqrt; i++) if (n % i == 0) continue search; // found a prime! holder.innerHTML += (n + ''); } document.getElementById('time').innerHTML = ((new Date).valueOf() - startTime);One of the FireFox versions was complaining about the script running too long so I also decided to do a second test, this one only going up to the number 5000.
Complete browser version list for test:
IE8 8.0.7600.16385 (32 and 64 bit)
IE9 Platform Preview 1.9.7766.6000
Chrome 5.0.375.55 beta
Chromium 6.0.420.0 (48547)
Firefox-32bit 3.6.3
Unofficial Firefox Namoroka/3.6.3 (64 bit) from http://wiki.mozilla-x86-64.com/Firefox:Download
Firefox-32-3.7a5pre Nightly Built on 19-May-2010
Times in ms for 5000:
IE8-32 | 2539 |
IE8-64 | 2954 |
IE9-32 | 1556 |
Chrome 5 | 752 |
Chromium 6 | 635 |
Firefox-32 | 5669 |
Firefox-64 | 5520 |
Firefox-32-3.7a5pre | 920 |
Times in ms for 10000:
IE8-32 | 6368 |
IE8-64 | 5733 |
IE9-32 | 5048 |
Chrome 5 | 2481 |
Chromium 6 | 2051 |
Firefox-32 | 30163 |
Firefox-64 | 29002 |
Firefox-32-3.7a5pre | 2830 |
Note I did tell FF to stop dialog'ing about the script taking a while so these oddly high times don't include me clicking the No button for the warning. Thus, I really have no explanation for the obscure duration for FF 32 and 64 to calculate under the 10000 limit.
IE8 also beats Firefox in both tests by considerable margins. Something I find to be rather strange as Firefox has native code compilation for Javascript whereas IE8 does not.
Also of note, in the 5000 limit, IE8-64 actually takes longer than IE8-32. Elsewhere the 64 bit browser out-performed its 32-bit brother but only marginally. Keep in mind, this is a pure mathematical JS test. A more robust test would probably include things like heavy DOM manipulation and HTML tree searching. So again, interesting results but nothing too conclusive regarding 64-bit browsers being extra powerful.
Some graphs:
Comments