This is the Part II of Benchmarks between Safari 3.1’s JavaScript engine and Firefox. Last Benchmark was done against Firefox 2, and Safari destroyed Firefox’s Javascript engine, in some aspects being up to 7 times faster.
So I was curious and I downloaded and tried the benchmark on Firefox 3.0b4. to see how much Firefox 3.0 will improve its Javascript performance, key to today’s web applications and the future of the web.
After seeing the results, I say Kudos to the Firefox 3 team, they’ve improved considerably their JavaScript engine and that only makes me glad cause I won’t have to switch to Safari. 🙂
I will not make any tests on HTML rendering, if you find any benchmark results on HTML rendering, please leave links on the comments section.
Once again, here are the results side by side:
FIREFOX 3.0b4
========================
RESULTS
(means and 95% confidence intervals)
-----------------------------------------
Total: 3876.6ms +/- 0.9%
-----------------------------------------
3d: 489.0ms +/- 1.3%
cube: 193.8ms +/- 1.2%
morph: 138.2ms +/- 1.5%
raytrace: 157.0ms +/- 3.8%
access: 594.2ms +/- 5.6%
binary-trees: 57.4ms +/- 5.9%
fannkuch: 246.0ms +/- 0.8%
nbody: 219.8ms +/- 13.6%
nsieve: 71.0ms +/- 2.1%
bitops: 470.4ms +/- 0.7%
3bit-bits-in-byte: 67.8ms +/- 1.5%
bits-in-byte: 90.8ms +/- 1.8%
bitwise-and: 177.4ms +/- 1.1%
nsieve-bits: 134.4ms +/- 0.5%
controlflow: 42.4ms +/- 1.6%
recursive: 42.4ms +/- 1.6%
crypto: 257.2ms +/- 1.2%
aes: 87.4ms +/- 1.3%
md5: 83.8ms +/- 4.0%
sha1: 86.0ms +/- 0.0%
date: 412.0ms +/- 0.4%
format-tofte: 251.6ms +/- 0.6%
format-xparb: 160.4ms +/- 0.4%
math: 502.0ms +/- 2.2%
cordic: 188.0ms +/- 0.5%
partial-sums: 231.2ms +/- 5.2%
spectral-norm: 82.8ms +/- 3.6%
regexp: 275.6ms +/- 1.0%
dna: 275.6ms +/- 1.0%
string: 833.8ms +/- 0.7%
base64: 98.6ms +/- 1.4%
fasta: 228.8ms +/- 3.2%
tagcloud: 166.2ms +/- 0.6%
unpack-code: 218.6ms +/- 0.5%
validate-input: 121.6ms +/- 0.6%
|
SAFARI 3.1
========================
RESULTS
(means and 95% confidence intervals)
-----------------------------------------
Total: 3368.8ms +/- 1.0%
-----------------------------------------
3d: 414.8ms +/- 1.9%
cube: 132.2ms +/- 2.4%
morph: 144.6ms +/- 4.1%
raytrace: 138.0ms +/- 0.6%
access: 520.4ms +/- 4.1%
binary-trees: 78.6ms +/- 11.3%
fannkuch: 231.4ms +/- 2.0%
nbody: 149.2ms +/- 8.1%
nsieve: 61.2ms +/- 3.9%
bitops: 449.6ms +/- 2.4%
3bit-bits-in-byte: 69.8ms +/- 9.6%
bits-in-byte: 99.2ms +/- 4.6%
bitwise-and: 167.2ms +/- 2.3%
nsieve-bits: 113.4ms +/- 6.7%
controlflow: 91.2ms +/- 4.7%
recursive: 91.2ms +/- 4.7%
crypto: 247.2ms +/- 2.3%
aes: 81.2ms +/- 2.5%
md5: 83.8ms +/- 4.6%
sha1: 82.2ms +/- 2.0%
date: 306.4ms +/- 0.5%
format-tofte: 146.6ms +/- 1.4%
format-xparb: 159.8ms +/- 1.0%
math: 454.8ms +/- 1.3%
cordic: 174.4ms +/- 1.6%
partial-sums: 193.8ms +/- 1.2%
spectral-norm: 86.6ms +/- 4.4%
regexp: 209.6ms +/- 0.7%
dna: 209.6ms +/- 0.7%
string: 674.8ms +/- 2.2%
base64: 103.8ms +/- 9.0%
fasta: 177.0ms +/- 1.0%
tagcloud: 136.0ms +/- 4.6%
unpack-code: 136.0ms +/- 1.7%
validate-input: 122.0ms +/- 2.6%
|
Almost there. Only in Flow control and recursion it beats Safari, the rest needs to improve, however, it’s improved a lot comparing to the previous version of Firefox.
The machine used for this test is a MacBook Pro running Mac OS X Version 10.4.11 with a 2.33 GHz Intel Core 2 Duo and 2GB 667 MHz DDR2 SDRAM.
I think that if you will doi the benchmarks on a 10.5 OSX the results will be diifferent. What do you think?