|Firefox 3.1b1 jit disabled (Mac)
|Firefox 3.1b1 jit enabled (Mac)
|Firefox 3.1b1 jit disabled (Win)
|Firefox 3.1b1 jit enabled (Win)
Once again, lower is better. I don’t know why, but TraceMonkey is clearly slower here (about half speed!) making it one of the slowest browsers I’ve tested. Maybe it’s something odd about my test setup. The first two runs are on my Mac Mini running Mac OS X v10.5.5, 1.83 GHz Intel Core 2 Duo, 1 GB 667 MHz DDR2 SDRAM, and the last two are on my Windows Box running Windows Vista SP1 64bit, Intel Core2 Duo 3.0 GHz, 4GB RAM.
On the bright side, this beta is slightly faster than Firefox 3.0.3 when TraceMonkey is disabled. Hopefully this test doesn’t indicate the results we’ll se in the final version of Firefox 3.1.
To run the test, I ran five auto-play games (computer plays both black and white), calculating the average time per move in each game (in milliseconds). I then averaged these times across the five different games to come up with the score for each browser.
Results (lower is better):
The first three tests were run on my Mac Mini running Mac OS X v10.5.5, 1.83 GHz Intel Core 2 Duo, 1 GB 667 MHz DDR2 SDRAM.
The last four tests were run on my Windows Box running Windows Vista SP1 64bit, Intel Core2 Duo 3.0 GHz, 4GB RAM.
|Internet Explorer 7.0
None of the tests are exactly conclusive. There was quite a wide range between the best and worst times for each of the browsers, but they did tend to cluster near the average. I was a little surprised that Chrome wasn’t a lot faster than Firefox after reading other benchmarks and hype.
If you’d like you can try out the current version of the Go game here. Just remember, it’s not done and may be changing at any time. For archival purposes (in case I want to run the same test against future browsers), I’ve put my code in this file go_benchmark.zip. If you run any tests, please let me know what you find.