4 ms·
It's a bit unfair to mention Chrome performing poorly on these. Both are asm.js, which OdinMonkey is optimised for, V8 not. That said, I'm very excited about a
by fhd2 13y ago
It's a bit unfair to mention Chrome performing poorly on these. Both are asm.js, which OdinMonkey is optimised for, V8 not.
That said, I'm very excited about asm.js (using it, in fact) and the performance in FF 22 blows me away as well. The V8 team appears to be working on asm.js optimisations, so soon we can have a fair contest :)
The best thing about asm.js is that the optimisations are really optional, unless your application is actually CPU-bound. The Unreal Engine probably is, to some degree. A simple 2D game like the one I'm working on certainly isn't. Not seeing it run any faster with FF 22, it's already smooth in older versions.
- azakai 13y ago> It's a bit unfair to mention Chrome performing poorly on these. Both are asm.js, which OdinMonkey is optimised for, V8 not. Actually Chrome has been optimizing for compiled C++ for a long time - Google even added Mandreel code to the Octane benchmark - and for asm.js specifically (which is a particular type of compiled C++) in recent months, as you can track here http://arewefastyet.com/#machine=11&view=breakdown&suite=asmjs-ubench http://arewefastyet.com/#machine=11&view=breakdown&suite=asm... http://arewefastyet.com/#machine=11&view=breakdown&suite=asmjs-apps http://arewefastyet.com/#machine=11&view=breakdown&suite=asm...
- bdash 13y agoIt's a bit odd that arewefastyet.com stops showing results for JavaScriptCore when switching to the asm.js view.
- azakai 13y agoJSC is also missing on Mandreel in Octane. Maybe the JSC shell lacks typed arrays?
- kevingadd 13y agoIf memory serves, JSC does not have typed arrays. The developer of Impact had to add them manually.
- azakai 13y agoSafari does have typed arrays though. I guess added in the browser, not in JSC itself?
- bdash 13y agoNope, they work just fine from the `jsc` shell.
- azakai 13y agoThanks for the info. Then I am really curious why awfy does not manage to run them properly. Perhaps it does not build JSC correctly somehow? I think that code is here https://github.com/dvander/arewefastyet/blob/master/driver/builders.py#L70 https://github.com/dvander/arewefastyet/blob/master/driver/b... edit: btw, is there a simple way to build just the JSC shell on Linux? I can't find one.
- bdash 13y agoThat looks like everything's being built and run in the correct way for OS X. Is there an easy way to run the benchmarks from that repository against my own WebKit working copy without having to set up all of the server-side support that the main README talks about? If I can run things locally I might be able to spot what's going awry with the asm.js tests for JSC. I'm not familiar with building just JSC on Linux, but last time I looked in to it the only way to build JSC was as part of building all of WebKit.
- azakai 13y agoYeah, basically each benchmark there has a python script to run it. For example in benchmarks/asmjs-apps it is possible to run python harness.py [SHELL_NAME] and it runs all the benchmarks in that directory using that shell. Regarding building, I've tried to build all of the Qt port on Linux (what the online guides mention), but always fail in the dependencies. Perhaps I'll try the gtk port.
- bdash 13y agoFrom what I can tell, JavaScriptCore has had typed array support since at least as far back as December 2011 (http://trac.webkit.org/r103637 http://trac.webkit.org/r103637, a random change in JavaScriptCore involving typed arrays).