未加星标

A first look at WebAssembly performance

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二05 | 时间 2017 | 作者 红领巾 ] 0人收藏点击收藏

WebAssembly gives us the promise to run high performance code in the browser in a standardized way. Now that there are a few WebAssembly previews available I decided it’s time to take a look at theirperformance. One source for benchmarks is the well known Computer Language Benchmarks Game and I decided to pick nbody (it’s almost four years ago since I did so last time…).

After playing a bit with the results I decided to put the codeon github . I’m looking forward to your corrections, improvements and feedback. I’m already excited what the results will look like in a few months…

The following versions were compared:

webAssembly: A WebAssembly version compiled from the original c version, because this turned out to be faster than the other version I checked object: The fastestjavascript version from the Computer Language Benchmarks Game. It uses a javascript objects for each bodyto store the data. arrayPerObject: Each body’s data isstored in a plain javascript array. floatArrayPerObject: Each body’s data is stored in a typed array oneTypedArray: All body’s data is stored in a single typed array and the advance function is programmatically unrolled (quite crazy, isn’t it). To get a baselinethe fastest java and the original c version were added.

Here are the results:


A first look at WebAssembly performance

Firefox does pretty well. The WebAssembly implementationis the fastest browser version and close to the java baseline, but the pure javascript implementation isn’t really much behind. Seems like Javascript VMs are already pretty good at simple numeric code.

For the other browsers WebAssembly couldn’t beat the javascript versions yet. And Safari has a completely different ideawhatJavascript version it can optimize best.

The fine print

Browser versions:

Chrome Canary,58.0.3004.0, invoked with

--js-flags="--turbo --trace-opt --trace-deopt --trace-bailout"

for turbofan and

--js-flags="--trace-opt --trace-deopt --trace-bailout"

for crankshaft.

Firefox 53.0a2 (2017-02-06) (64-Bit) Safari Technology PreviewRelease 22 (Safari 10.2, WebKit 12604.1.4.2)

WebAssembly setup:

Emscripten and Binaryenwere installed as described on Compile Emscripten from Source . (emcc (Emscripten gcc/clang-like replacement) 1.37.2 (commit 70d370296036cc5046083a3e215cb605c90e004b)) The c source code was compiled with that command:
emcc nbody.c -O3 -s WASM=1 -s SIDE_MODULE=1 -o nbody.wasm

C compiler:

The c version was compiled withgcc -O3 nbody.c -o nbody (which isApple LLVM version 8.0.0 (clang-800.0.42.1))

This version took 4.4 seconds on my machine and was faster than the fastest C version from the shootout, compiled withgcc -O3 -fomit-frame-pointer -march=native -mfpmath=sse -msse3 nbody_fastest.c -o nbody_fastest, which took 4.9 seconds on my machine

Infrastructure:

All tests were performed on a 2015 MacBook Pro,2.5 GHz Intel Core i7,16 GB 1600 MHz DDR3. For all tests the best of three runs was selected for the result.

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

主题: JavaMacBookAppleChromeDUFirefoxLV
分页:12
转载请注明
本文标题:A first look at WebAssembly performance
本站链接:http://www.codesec.net/view/531088.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(51)