zandaqo/iswasmfast
View on GitHub ↗ ★ 196 JavaScript
Performance comparison of WebAssembly, C++ Addon, and native implementations of various algorithms in Node.js.
5 mentions on Hacker News by 2 people: 0 stories, 5 comments · first 2018-10-22 · latest 2022-02-01
20082026
-
At a glance, the bindings for wasm copy the data, https://github.com/zandaqo/iswasmfast/blob/54bbb7b539c127185... If the running code is short enough then that copy might easily make the wasm version much slower. That is indeed a known…
comment by azakai · 2022-02-01 · in Pay attention to WebAssembly -
…between 1.45 and 1.55 times slower than native code, but results do vary by runtime. Yeah, nah: https://github.com/zandaqo/iswasmfast JS is about 10x faster than wasm in simple linear regression, and 30% faster in levenstein distance…
comment by maga · 2022-01-31 · in Pay attention to WebAssembly -
…might become the best approach for computationally heavy tasks. I wrote about it a bit here[2]. [1] https://github.com/zandaqo/iswasmfast [2] https://medium.com/swlh/structurae-1-0-graphs-strings-and-we...
comment by maga · 2021-04-20 · in Node.js 16 Available Now -
A few years ago I did similar comparison but in context of Node.js and sans manual optimizations: https://github.com/zandaqo/iswasmfast In my work, I have come to conclusion that it seldom pays off to go "native" when working with Node.js.…
comment by maga · 2021-04-14 · in Is WebAssembly magic performance pixie dust? -
I have done some benchmarking comparing JS, WASM, and native C++ addon performance in Node.js: https://github.com/zandaqo/iswasmfast From the look of it, in Node.js, WASM suffers less data exchange overhead while been decently close to…
comment by maga · 2018-10-22 · in WebAssembly’s post-MVP future