I ran my browsers through these JavaScript benchmark tests. All tests ran on my 1ghz PowerBook G4. Very surprising results:
Test 1 | Test 2 | Test 3 | Test 4 | Test 5 | Test 6 | Test 7 | Total | |
---|---|---|---|---|---|---|---|---|
Camino 0.7 | 2.042 | 1.378 | 2.521 | 1.656 | 0.680 | 8.890 | 1.966 | 19.130 |
Firefox 0.8 | 18.011 | 4.161 | 2.371 | 1.944 | 0.756 | 12.613 | 2.160 | 42.020 |
IE 5.2 | 1.849 | 0.693 | 3.325 | 42.444 | 2.898 | 10.787 | 5.227 | 67.220 |
Safari 1.2 | 67.403 | 1.929 | 1.848 | 25.723 | 14.694 | 5.023 | 16.179 | 132.800 |
I use Camino as my main browser but I had no idea the JavaScript performance was that much better. Anyone else have similar/different results?
Very interesting. I use MyIE2 and it did MUCH better than IE does:
Internet Explorer 5.x
67.95 seconds
13 results
Internet Explorer 5.5x
44.05 seconds
5 results
Internet Explorer 6.x
42.51 seconds 215 results
MyIE2
17.24 seconds
15 results
My test completed in about 23 seconds overall, the first text taking a good 60% of that. 🙂
BTW – only tested MyIE2, but it’s very good to know that just ’cause it’s based on IE doesn’t mean that it has to suck as much as IE does. 😀
Holy crap! That’s really impressive.
Tell me, what is the actual difference between Camino and Firefox?
Camino uses native Mac OS X widgets and the UI is written in Cocoa.
I like the “feel” better than Firefox, but it doesn’t have accesskey support and Firefox does.
Tests on a 2.4Ghz P4, Windows XP
Firefox:
TEST 1 time: 7.718 sec.
TEST 2 time: 1.234 sec.
TEST 3 time: 0.922 sec.
TEST 4 time: 0.594 sec.
TEST 5 time: 0.36 sec.
TEST 6 time: 4.875 sec.
TEST 7 time: 2.094 sec.
Total: 17.797 seconds
IE 6:
TEST 1 time: 7.5 sec.
TEST 2 time: 5.703 sec.
TEST 3 time: 1.047 sec.
TEST 4 time: 0.735 sec.
TEST 5 time: 0.656 sec.
TEST 6 time: 1.812 sec.
TEST 7 time: 1.313 sec.
Total: 18.766 seconds
[edited, totals added by Alex]
I have read elsewhere that turning off all languages other than English in Safari (by selecting the Safari App in Finder and doing a GetInfo) can significantly speed up Safari. Has anyone tested this? Does it bring Safari up to Camino speeds?
I love Camino, by the way, and use it as my default browser, but it does crash a lot which is annoying.
I’ve had nightlies in the last few months that were a little crash happy but I’m currently using a nightly from a week or two ago that has never crashed (knock on wood).
i love camino! (my default browser for a VERY long time) it’s great to know it’s javascript is way up there…
now if it could only display some pages, like ESPN’s properly, i would never have to use safari! (:
and oh– i got about 11.7 seconds running that test with about 20 apps running
So basically Camino is Firefox for OS X? (roughly speaking :)).
Sort of, both projects started the same way.
is there a place where we can commend the developers of Camino?
I have always liked this browser and want to see them continue development on it.. thanks!
Their feedback page is probably a good place to start.
Mac JS
Alex King did some Javascript performance tests on a variety of Mac browsers: Apple’s Safari, the Gecko-based Camino and Firefox, and the now-defunct Microsoft Internet Explorer. 24fun’s Javascript Speed Tests were used. Camino came out on top. I’m …
Remeber how Apple was claiming that Safari was something like 67% faster than anything else for JavaScript performance?
Apparently they’re sticking to it – Safari is 28.4% faster than NS7.
JS performance involves many things. If you were to count just javascript execution of something like strings, Mozilla (and NS7) would far out perform safari. Their test is skewed. Ordinarly folks will see the 28.4% faster and think it sounds good, and probably won’t see what a load of BS it is.