3 ms·
28ms on 2018 iPhone without threads or SIMD, 24ms on Chrome MBP 2019 with threads and no SIMD, 11ms with SIMD.
by dzhiurgis 6y ago
28ms on 2018 iPhone without threads or SIMD, 24ms on Chrome MBP 2019 with threads and no SIMD, 11ms with SIMD.
- skohan 6y agoWhat's the use-case for tensorflow on web/mobile web? I thought tensorflow was mostly for training models, and my assumption would be that this is mostly relevant for the server/workstation context, but maybe I'm missing something
- netheril96 6y ago> I thought tensorflow was mostly for training models You need tensorflow to actually use the models trained with tensorflow.
- the_svd_doctor 6y agoWhy? You could export your weights and everything into any other framework, no?
- hansvm 6y agoProbably, but looking at that chain of comments I think the emphasis was that you need _something_ like tensorflow to do inference client-side using pre-trained models, not that you need _tensorflow_ specifically to operate on tensorflow models.
- gridlockd 6y agoTensorflow-JS is that framework that you export to from Tensorflow. Tensorflow-JS is not Tensorflow, it's just the same brand.
- postalrat 6y agoWouldn't you need the topology as well?
- alquemist 6y agoSome people care to deliver ML-enhanced services without peeking over the shoulder of their users for every keypress. Client inference performance matters.
- dzhiurgis 6y agoI was curious of iPhone performance - looks like latest one will outperform my MacBook again...