News for hackers. Stuff that matters.

A comment on Replacing JavaScript Hot Path with WebAssembly. Parent comment

Re:Replacing JavaScript Hot Path with WebAssembly by robko on Thursday February 14, 2019 @06:38PM (#19167143)
You are correct. The code is using an inefficient cache access pattern, so most of the time is spent waiting.

You probably won't get 100x faster without SIMD, but 10x is certainly doable. Unfortunately, SIMD.js support has been removed from Chrome and Firefox a while ago, even though it is not available in wasm to this day.

[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by kllrnohj on Thursday February 14, 2019 @06:57PM (#19167266)
How would SIMD do anything to address the problem's fundamental anti-cache-friendly access patterns? You'd need to restructure the problem to be cache-friendly, but SIMD won't really be relevant to that.
[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by robko on Thursday February 14, 2019 @07:26PM (#19167458)
You can use both at once. Usually, you'd have something like 64x64 tiles in cache and use 4x4 or 8x8 tiles for SIMD.
[ Parent | on HN ]