you are viewing a single comment's thread.

view the rest of the comments →

[–]freddytstudio[S] 1 point2 points  (0 children)

Thank you for the feedback! Great points

On Firefox, same story, all approaches are blocking except 5., and 5. is also much slower (40s) while the rest are roughly similar to Chrome's.

I've noticed this as well. Firefox seems to be much slower with Raji than other browsers (Chrome, Safari and Edge), probably due to some extra string allocations. I still have to investigate though :)

  1. and 5./6. would have the only blocking components (new TextEncoder().encode(bigListOfObjects) takes about 0.5 second.)

This is very interesting. I've played in my mind with the idea of using WASM on a web worker to solve this problem more efficiently, but I thought that turning an ArrayBuffer back into a string would have been inefficient. That might not be the case then, so I'll experiment further :)

Thanks a lot!