Replies: 5 comments 15 replies
-
|
Frigate 0.11 has a new ffmpeg build so if it is still occurring then seems to be expected or a deeper issue. That graph isn't super helpful, a screenshot of What resolution are your cameras? It is entirely possible that it is less work to decode the stream for the CPU (when you factor in the CPU usage needed to move the stream to / from GPU) if the cameras are low enough resolution |
Beta Was this translation helpful? Give feedback.
-
|
I noticed something similar with one of the earlier betas. Depending on which qsv arguement I used the CPU usage varied enormously. The old style args were less CPU intensive than the new but that's now reversed since beta 7. More info in #3482 . I'm now using vaapi over qsv as for some reason that lowered it even further. There is a discussion somewhere about that but I can't find it ATM. |
Beta Was this translation helpful? Give feedback.
-
|
Just to add to this as I'm testing Frigate out right now. Using a Raspberry Pi 4B 4GB with two cameras to test with. Without hwaccel the CPU usage sits at around 35-45%, but if I enable it it shoots up to 85-90%. I'm deploying frigate with the helm chart on a k3s cluster btw, but specifying the tag to be The following shows the CPU graph from Netdata running on the node, right around the middle I restart the process to turn hwaccel of: I'm just trying to set directly on the cameras, or globally, running Happy to debug further for more info. |
Beta Was this translation helpful? Give feedback.
-
|
Yes I am seeing the same thing and have been scratching my head over it for a few days 1 stream at 1080p without hwaccel, ~25% cpu with hwaccel (h264_v4l2m2m) ~75% cpu I dont have a benchmark to compare it against in past releases because ffmpeg was crashing after a few minutes with any of the hwaccel settings, now it runs longer just with a very high cpu usage |
Beta Was this translation helpful? Give feedback.
-
|
I did some more testing based on various comments made in this thread: General Troubleshooting
Tested 2x 1920x1080 camera streams W/O hwaccel and WITH hwaccel:
Tested 1x 2560x1920 camera stream W/O hwaccel and WITH hwaccel:
|
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Curious if anyone else has seen their CPU usage actually go up when they enable HW Accel on a 64-bit OS Docker instance via Raspberry Pi 4? (h264_v4l2m2m).
This has been a problem ever since I first set up frigate, was hoping the new 0.11.0-rc1 release would magically fix it but alas it's having the same issues.
GPU memory is set to 256 and shm is set to 600mb which should be more than enough for the 3x cameras I'm running. Confirmed my docker image is running in priveleged mode, also mapped all of the /dev/video* into the docker container in case that was necessary.
Tried applying hw_accel globally and also only applying the hw_accel args to the input stream/decode of specifically a few 1080p cameras (since the official raspberry pi documentation suggests thats the limit of decoding hw accel support)
Any other suggestions/things to try would be appreciated!
Here's a plot of CPU usage without any hw_accel arguements and after I turn it on.

Beta Was this translation helpful? Give feedback.
All reactions