One of the reasons minih264 is so fast when running from C/C++ is because of multithreading support, which is disabled in the WASM builds. In browsers with SharedArrayBuffer, it should be possible to enable multithreading. As far as I'm aware, I'll need yet another WASM build target for this, so .shared.wasm and .shared.simd.wasm ... But maybe there is another approach.
Something I'm not sure about is the future/status of SharedArrayBuffer, as there was some concerns it might get removed or changed due to security reasons.
One of the reasons minih264 is so fast when running from C/C++ is because of multithreading support, which is disabled in the WASM builds. In browsers with SharedArrayBuffer, it should be possible to enable multithreading. As far as I'm aware, I'll need yet another WASM build target for this, so
.shared.wasmand.shared.simd.wasm... But maybe there is another approach.Something I'm not sure about is the future/status of SharedArrayBuffer, as there was some concerns it might get removed or changed due to security reasons.