3 ms·
They disable vectorization on native, so hard to call this a true apples-to-apples comparison
by hackcasual 8y ago
They disable vectorization on native, so hard to call this a true apples-to-apples comparison
- Veedrac 8y agoIt makes sense since WASM's SIMD isn't ready yet, and a paper saying “WASM is slower because SIMD isn't ready yet” would be rather uninformative to browser vendors.
- hackcasual 8y agoI think the problem when you're doing X vs. native is you're implicitly saying "X vs. the best possible situation." I think it's fine to compare it against vector-less operations, but they should also benchmark against more vanilla native compiler settings.
- vanderZwan 8y ago> when you're doing X vs. native is you're implicitly saying "X vs. the best possible situation." Not really, any sensible benchmark would be "X vs. the most relevant point of comparison".