If equivalent WASM'd crypto methods are outperforming native ones, can we at least agree that's a problem worth solving?
Although I shouldn't have to say so, we're all aware of jank. It's an issue for network I/O threads too, not just UI responsiveness (network I/O jank ultimately leads to UI jank) and we wouldn't do it this way if it were actually problematic.
-
-
Suggestion: Pick your max acceptable latency for a blocking op. Take your worst-performing (mobile) device. Measure how many crypto ops (e.g. 1KB SHA-256, 4KB AES-GCM) operations you can do within that window. You can approximate this by just running `bssl speed` on your laptop.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.