On my machine given my unscientific measurements in Q2 2009:
V8 and JavaScriptCore are really, really fast.
TraceMonkey is fast, but often far behind really, really fast.
V8: Chromium 3.0.182 (182.0) snapshot 16837 23 May 2009
TraceMonkey: Firefox 3.6a1pre nightly latest-trunk 22 May 2009
JavaScriptCore (SquirrelFish extreme): WebKit r44078 nightly 23 May 2009
- Dromaeo JavaScript Tests (higher is better):
- V8: 175 runs/s
- JavaScriptCore: 195 runs/s
- TraceMonkey: 53 runs/s
- V8: 175 runs/s
- V8 Benchmark Suite version 4 (higher is better):
- V8: 2324
- JavaScriptCore: 1882
- TraceMonkey: 289
- V8 Benchmark Suite version 3 (higher is better):
- V8: 2109
- JavaScriptCore: 2079
- TraceMonkey: 281
- SunSpider 0.9 (lower is better):
- V8: 859ms
- JavaScriptCore: 860ms
- TraceMonkey:1430ms
For the SunSpider bars lower is better, for the others higher is better. Read the previous post for more information.
Thanks for the update. Pity of the Neanderthal comments here, ignore 'm :-)
ReplyDeleteThis is super cool, but the similarity of speed makes me wonder if they hit a wall. Is the the next in a long line of substantial increases in javascript speed, or the last significant squeezing of speed out of a language that can't be optimized much more.
ReplyDeleteThanks. I have deleted those and from now on only registered users can comment so it shouldn't happen again. It shows that people with only half a brain can use a web browser which is both a good and bad thing, I guess.
ReplyDeleteDavid I don't think so. All of the benchmark suites consists of a number of tests and if you dig deeper into those you'll find cases where V8 and JSC are currently very different in speed. That alone is an indication of remaining optimization headroom.
ReplyDeleteAnd then benchmarks are just benchmarks..
Makes me wonder how close these are to optimized c code?
ReplyDeleteThe performance of JavaScript engines is now excellent, but the dirty little secret of browsers is that DOM performance is *not*. In many applications the DOM is now the bottleneck, not JavaScript execution.
ReplyDeleteIf we want to see JavaScript replace Flash for graphics intensive applications like games a lot of work will be need to be done in optimizing DOM operations.