Closed abhajaswal closed 2 years ago
Hi @abhajaswal
The preparation time for CPU and GPU includes time taken to compile the kernels used by those backends. This can be quite time consuming but only occurs once.
Yesterday @morgolock gave some more information on the issue you raised on ComputeLibrary: https://github.com/ARM-software/ComputeLibrary/issues/977
Best regards, Mike
Thanks Mike , I will check this. You can close the issue from here I think , as the improvements would be seen on ARMNN automatically once ACL side optimizations are done
Dear team,
I try to run mobilenetv2 model using ARMNN , but the prepare API for GPU target take 10 times more time than the CPU target
Tiime taken by ARMNN CPU to prepare : 992ms ARMNN GPU : 9607ms
Tiime taken by opensource tflite CPU plugin : 44ms
Could you let me know what could be the root cause? Does the pipline creation takes more time?
I need to review the usage of the ARMNN further for our Use case , but in case prepare takes lot of time then i need an understanding about it.