I'd love to see the numbers for the asm.js version running in Safari and Chrome
Which means the asm.js version is faster than other JS versions, even without specific asm.js optimizations.
21–30 of 44 posts
I'd love to see the numbers for the asm.js version running in Safari and Chrome
Which means the asm.js version is faster than other JS versions, even without specific asm.js optimizations.
Not too useful as does not include one of the very popular ports and an additional major platform: http://farseerphysics.codeplex.com/ :(
Not too useful as does not include one of the very popular ports and an additional major platform: http://farseerphysics.codeplex.com/ :(
Earlier quoted context omitted.
To answer my own question, I got: gcc 4.6.3: 3.554688 +/- 4.786550 clang trunk: 3.593750 +/- 4.798172 Chrome: 41.03515625 +/- 9.331709130062185 Which puts Chrome at about 11x these native compilers, consistent with the blog post.
gcc 4.8.0: 1.640625 +/- 3.703323 clang 3.2: 1.718750 +/- 3.772718 chrome : 23.28515625 +/- 3.636932727324763 So chrome is about ~14x the native compilers. Changing gcc to use -O2 instead of -O3 gets: 1.562500 +/- 3.630922.
Interesting that NaCl is far closer to native performance than asm.js. Can that performance gap be closed?
Interesting that NaCl is far closer to native performance than asm.js. Can that performance gap be closed?
I'm not sure I'd call that "far" different, but asm.js is certainly in early stages so it probably will get faster.
C (gcc 4.2.1) 2.62 +/- 0.24 1.0x
NaCl (x86-32) 3.39 +/- 0.25 1.3x
asm.js (Firefox Nightly) 5.12 +/- 0.59 1.9x
NaCl is 30% slower, asm.js is 90% slower.Earlier quoted context omitted.
I'm not sure I'd call that "far" different, but asm.js is certainly in early stages so it probably will get faster.
C (gcc 4.2.1) 2.62 +/- 0.24 1.0x NaCl (x86-32) 3.39 +/- 0.25 1.3x asm.js (Firefox Nightly) 5.12 +/- 0.59 1.9x NaCl is 30% slower, asm.js is 90% slower.