Comment by theultdev
1 hour ago
yeah turns out it was chrome that was slow, not firefox.
wasm hashing in chrome is half the speed of firefox.
asmjs with optimizations enabled in firefox are about on par, which supports your statement.
1 hour ago
yeah turns out it was chrome that was slow, not firefox.
wasm hashing in chrome is half the speed of firefox.
asmjs with optimizations enabled in firefox are about on par, which supports your statement.
No comments yet
Contribute on Hacker News ↗