News for hackers. Stuff that matters.

A comment on Pixel Visual Core: Google’s first custom-designed co-processor. Parent comment

Re:Pixel Visual Core: Google’s first custom-designed co-proc... by joshuamorton on Wednesday October 18, 2017 @12:05PM (#15500306)
I'm really confused why you keep bringing up opencv. What does opencv have to do with the (presumably) TF ML model running on the IPU that you want to benchmark against the TF ML model running on a GPU?
[ Parent | on HN ]
Re:Pixel Visual Core: Google’s first custom-designed co-proc... by sandGorgon on Wednesday October 18, 2017 @12:55PM (#15500744)
Because halide is positioned as a high performance improvement over opencv. While I believe it is just an architectural decision to enable a non-portable ML model.
[ Parent | on HN ]
Re:Pixel Visual Core: Google’s first custom-designed co-proc... by trishume on Thursday October 19, 2017 @10:52AM (#15508407)
But Halide does have higher performance, is portable to many platforms as well as GPUs, CPUs (w/ parallel SIMD), and isn’t used for ML models...
[ Parent | on HN ]
Re:Pixel Visual Core: Google’s first custom-designed co-proc... by joshuamorton on Wednesday October 18, 2017 @02:57PM (#15501903)
Where did I mention halide?

My question is why do you care about opencv when benchmarking neural network performance on various hardware?

[ Parent | on HN ]