undefined

points

[-]

> Mostly because 3P support has not been a engineering priority.

Got it: assuming you're at Google, in eng. parlance, it's okay if it's not Prioritized™ but then product/marketing/whoever shouldn't be publishing posts around the premise it's running 60 fps multimodal experiences on device.

They're very, very, lucky that ratio of people vaguely interested in this, to people follow through on using it, is high, so comments like mine end up at -1.

by my12318 hours ago|

parent|

[-]

Tensor is essentially shipping subpar hardware with not even taking care of software properly.

https://ai.google.dev/edge/litert/android/npu/overview has been identical for a year+ now.

In practice Qualcomm and MediaTek ship working NPU SDKs for third party developers, NNAPI doesn't count and is deprecated anyway.

by refulgentis16 hours ago|

parent|

[-]

Man this is a funny situation. Ty for sharing, more or less confirms my understanding. Couldn't quite believe it when I was in Google, or out of Google. This should be a big scandal afaict. What is going on???

(n.b. to readers, if you click through, the Google Pixel Tensor API is coming soon. So why in the world has Google been selling Tensor chips in Pixel as some big AI play since...idk, at least 2019?)

by my12315 hours ago|

parent|

[-]

Yes, you can use first-party models on the Pixel NPUs or you're stuck with NNAPI which is self-admittedly deprecated by Google and doesn't work all that well.

On third party model workloads, this is what you will get:

https://ai-benchmark.com/ranking.html

https://browser.geekbench.com/ai-benchmarks (NPU tab, sort w/ quantisation and/or half precision)

Google is clearly not serious on Pixels in practice, and the GPU performance is also behind by quite a lot compared to flagships, which really doesn't help. CPUs are also behind by quite a lot too...