News for hackers. Stuff that matters.
Re:Automerge 2.0 by lll-o-lll on Monday January 30, 2023 @11:30PM (#34591132)
Wow, 3x perf penalty? I thought wasm was supposed to get us to “near native speeds”. Is this typical of the penalty paid, or something specific to automerge?
Re:Automerge 2.0 by josephg on Tuesday January 31, 2023 @12:02AM (#34591392)
Yep. At least, thats the slowdown rate I saw porting my own (very optimized) CRDT to wasm last year. I haven't measured automerge's wasm build but 3x slower is a reasonable baseline for wasm's performance compared to x86_64 code.

Some of that difference is a lack of auto-vectorization in wasm. Wasm SIMD is pretty new, and not well supported in wasm runtimes yet as far as I know.