3 ms·
> Making each webapp target & optimize ML for every possible device target sounds terrible. Yes it does. Did something I said imply that? OpenXLA is an inter
by nl 4y ago
> Making each webapp target & optimize ML for every possible device target sounds terrible.
Yes it does.
Did something I said imply that?
OpenXLA is an intermediate layer that frameworks like PyTorch or JAX can use. It has pluggable backends, and so if there was a web-compatible backend (WebGL or WASM) then everyone could use it and all models that were built using something that used OpenXLA[1] would be compatible.
[1] Not 100% sure how low-level the OpenXLA intermediate representation is. I know it's not uncommon when porting a brand new primitive (eg a special kind of transformer etc) to a new architecture (eg CUDA->Apple M1) that some operations aren't yet supported, so this might be similar.
- rektide 4y agoI support having web targets. It'd be a good offering. But it feels upside down to me from what we really all should want, which is a safe way to let the web target any backend you have. WebGPU or WebGL or wasm are going to be OK targets, but with limited hardware support & tons of constraints that mean they won't perform as well as openxla. Also how will these targets get profiled? Do we ship the same WebGL to a 600w monster as a rpi? There's a lot of really good reasons to want OpenXLA under the browser, rather than above/before it.