3 ms·
Based on George Hotz's testing it is very broken. It's possible it has improved since then, I guess but he streamed this a few weeks ago.
by sebzim4500 4y ago
Based on George Hotz's testing it is very broken. It's possible it has improved since then, I guess but he streamed this a few weeks ago.
- dagmx 4y agoIt supports a subset of the operators (as mentioned in the release notes). I don’t think it’s broken for the ones that it does support though.
- norgie 4y agoYes, this is my experience. Many off the shelf models still don't work, but several of my own models work great as long as they don't use unsupported operators.
- mochomocha 4y agoThat's been my experience. However when fallback to CPU happens, it sometimes end up making a specific graph execution slower. But that's explicitly mentioned by the warning and pretty much expected.
- brucethemoose2 4y agoYou'd think it would fall back to GPU/CPU for unsupported operations instead of failing, but I guess thats easier said than done.
- rfw300 4y agoIn fact there is an environment variable that enables exactly that. There are obviously performance issues associated with that, but it does work.
- bigbillheck 4y ago[flagged]
- microtonal 4y agoWe tested inference for all spaCy transformer models and they work: https://explosion.ai/blog/metal-performance-shaders https://explosion.ai/blog/metal-performance-shaders It depends very much on the ops that your model is using.
- laichzeit0 4y agoI could fine-tune a Detectron2 model a few months ago using PyTorch and MPS backend [1]. I'd be interested if it's working yet. https://github.com/facebookresearch/detectron2/issues/4342 https://github.com/facebookresearch/detectron2/issues/4342