iswasmfast

Performance comparison of WebAssembly, C++ Addon, and native implementations of various algorithms in Node.js. (by zandaqo)

Iswasmfast Alternatives

Similar projects and alternatives to iswasmfast

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better iswasmfast alternative or higher similarity.

iswasmfast reviews and mentions

Posts with mentions or reviews of iswasmfast. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-01-31.
  • Pay Attention to WebAssembly
    12 projects | news.ycombinator.com | 31 Jan 2022
    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 downside of wasm (calls to JS are somewhat slow, and copying of data even more so - wasm shines when you can avoid those things).

    If it's not that, then a 10x difference suggests you are running into some kind of a VM bug or limitation.

    12 projects | news.ycombinator.com | 31 Jan 2022
    > “Near-Native Performance”: Wasm is often described as having “near-native performance”. What this actually means is that WebAssembly is almost always faster than JavaScript, especially for compute-intensive workloads, and averages 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 calculation.

  • Node.js 16 Available Now
    5 projects | news.ycombinator.com | 20 Apr 2021
    WASM has its moments, as you can see in this[1] benchmark it outperforms JS and native addons on certain tasks.

    Since the bottleneck with native addons is usually data copying/marshalling, and we have direct access to WebAssembly memory from the JavaScript side, using WebAssembly on this "shared" memory might become the best approach for computationally heavy tasks. I wrote about it a bit here[2].

    [1] https://github.com/zandaqo/iswasmfast

  • Is WebAssembly magic performance pixie dust?
    8 projects | news.ycombinator.com | 14 Apr 2021
    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. More often than not, rewriting some computationally heavy code in C and sticking it as a native module yielded marginally better results when compared with properly optimized js code. Though, that doesn't negate other advantages of using said technologies: predictable performance from the start and re-using existing code base.

  • A note from our sponsor - InfluxDB
    www.influxdata.com | 28 Mar 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic iswasmfast repo stats
4
190
0.0
about 1 year ago
Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com