-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Object detection - CPU resources #18
Comments
@aaguiar96 Can you give some code snippets, as well as models used? It's a little hard to tell with the given info, but yes, most inference works will be delegated to the TPU (depending on the model). Keep in mind that input processing will be executed with the CPU. |
My main question is:
will this code be delegated to the USB Accelerator device? I'm using a retrained MobileNet model, compatible with the Thanks in advance. |
@aaguiar96 Hi, as far as I could tell, the code looks okay at glance. As for your retrained model, have you compiled it for the |
Yes, it is compiled for the I think this should not occur if the detection is running on the coral device. |
Hi, you're not wrong, when running inference after creating a DetectionEngine should automatically delegate works to TPU. However, I'm wondering if all operation were mapped to the edgetpu during compilation. Any operation that was not mapped to the tpu will be executed on the CPU, can you provide the log file generated by the edgetpu_compiler by any chance (it should give very nice details on which operations are mapped to the edgetpu and which are not)? |
Ok, you saved me... My bad! I did not compile the model. Thank you for your help. |
No problems! |
Hello,
I'm performing object detection in the same way as
classify_image.cc
but using thedetection engine
and doing it in a loop for several images.However, when I do so it consumes 100% of one of my CPU cores.
I didn't expect this since the detection is being executed on the USB accelerator. Right?
Thanks in advance.
The text was updated successfully, but these errors were encountered: