Re:WebAssembly Adoption: Is Slow and Steady Winning the Race?
by leptons on Wednesday April 10, 2024 @12:46PM
(#39992798)
Running FFMPEG in the browser through WASM is a game changer for me.
[ Parent
| on HN ]
Re:WebAssembly Adoption: Is Slow and Steady Winning the Race?
by chompychop on Wednesday April 10, 2024 @01:10PM
(#39993130)
But isn't it really slow (like 20x or so) than native FFMPEG?
Re:WebAssembly Adoption: Is Slow and Steady Winning the Race?
by lxgr on Wednesday April 10, 2024 @04:25PM
(#39995350)
I'd be very surprised. I haven't tried ffmpeg in WASM myself, but I do know that for Stockfish, a popular and very CPU-hungry chess engine, the difference is within 20-30% or so vs. an optimized native build.
Re:WebAssembly Adoption: Is Slow and Steady Winning the Race?
by leptons on Wednesday April 10, 2024 @06:49PM
(#39996502)
No, not for me. I'm not transcoding 8k videos with it or anything like that. My use case is extracting thumbnails and video color info, basically transcoding to raw 100px x 100px clips and grabbing color info from that. The user would rather it takes as long as it takes than have to charge them a subscription fee to host the transcoding in the cloud.
Re:WebAssembly Adoption: Is Slow and Steady Winning the Race?
by mc_woods on Wednesday April 10, 2024 @11:12PM
(#39998064)
Yup. WASM lacks the "domain specific" acceleration available to native code. So you miss out on any hardware codec support. Same is true for openSSL, there is a bunch of encryption acceleration in modern CPUs that WASM can't access at the moment.