[HW Accel Support]: High Detector CPU Usage using Intel iGPU Beelink EQ12 #20253
Replies: 2 comments 11 replies
-
|
Your inference time, while slightly high, does suggest that the GPU is being used for inference. CPU inference would be much slower. Detector CPU Usage is measuring the CPU required to prepare inputs for inference on the GPU. This task can't be offloaded to the GPU. I'd suggest tuning your motion detection. If your cameras are constantly detecting motion, for example, object detection will constantly run as Frigate looks for objects in areas of motion. This is one common explanation for a high Detector CPU Usage value. |
Beta Was this translation helpful? Give feedback.
-
|
What are your detect streams resolutions and fps? |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
Hi!
I'm running Frigate in docker on a Debian 13 LXC with passed through N100 iGPU (Intel Alderlake N Gen12), however Frigate only shows gpu usage for a little while if I restart the proxmox node and then shows 0.0% The detector CPU usage is always quite high (over 70%). I have 5 camera's typically running (2 x Reolink Duos, 1 x Reolink RLC-1224a and 2 x Eufy 2k indoor cams) and I'm using OpenVino with YOLOv9-S.
I'm not sure if this is too much for the system or if I've done something wrong but would appreciate some guidance.
Version
0.16.1-e664cb2
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Install method
Proxmox via Docker
Object Detector
OpenVino
Network connection
Mixed
Camera make and model
Reolink and Eufy
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions