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 vijaybritto on Friday February 15, 2019 @02:40AM (#19169180)
I think its fast because of the L1 cache or something like that. I dont understand fully but this is what i got
[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by acqq on Friday February 15, 2019 @02:42AM (#19169191)
The fastest version is the fastest because it's the most cache-friendly one of all which were presented. See e.g.

https://stackoverflow.com/questions/5200338/a-cache-efficien...

But note that robko made an improvement even before making that.

[ Parent | on HN ]
Re:Replacing JavaScript Hot Path with WebAssembly by acqq on Saturday February 16, 2019 @05:54AM (#19178095)
> made an improvement even before

Or maybe not: my short experiments with the simplified version based on their algorithm and his JavaScript versions gave some conflicting results. I haven't thoroughly verified them, this note is just to motivate the others to try.

[ Parent | on HN ]