[Beta Support]: high cpu after updating to 0.17.0-beta2 #21824
Replies: 7 comments 14 replies
-
|
After stopping the frigate add-on, the CPU drops to 27% |
Beta Was this translation helpful? Give feedback.
-
|
You have a number of issues:
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your suggestions I have changed the config as per point 2. However point 1. for "main_drive" the stream is rtsp TCP HVEC. The presets don't work with this camera. I am trying to re-encode it to h.264. |
Beta Was this translation helpful? Give feedback.
-
I had this working some what before in 0.16.0 |
Beta Was this translation helpful? Give feedback.
-
|
If you need to re-encode, you should use go2rtc - it's much easier. See the go2rtc docs: https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#source-ffmpeg Then, remove any manual arguments from your Frigate config. |
Beta Was this translation helpful? Give feedback.
-
|
I think this was configured 5 years ago or more before go2rtc and was never changed as it "kinda" worked, but not in all browsers or devices as I think I was using HVEC for streaming and for recording for main_drive. This worked for me but has gotten unusable in this version which is a blessing as now I have a more stable system (since the changes) in the earlier versions my CPU was quite low usage, lower than now (currently ~50%) as I was not transcoding main_drive. The resolution and FPS changes for detection has made a big difference especially in this version, and everything is detecting better because of the changes and I am using a sub stream for detection running at less resolution (because my CPU has spare capacity to do so) which drops a lot less frames . Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
@hawkeye217 Thank you. Everything is more stable, I think things were made worse as the watchdog was restarting because of the dodgy HVEC camera and the manual config and therefore making the CPU spike each time it restarted. Potential downside are:
|
Beta Was this translation helpful? Give feedback.
-
|
LPR and face recognition will likely not work at that low of a resolution, and object detection may suffer as well. |
Beta Was this translation helpful? Give feedback.
-
|
This is for detection, do you mean for the detection resolution? Or low camera resolution? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, if you set this: This means that:
The general recommended |
Beta Was this translation helpful? Give feedback.
-
|
Ah I see. Thank you. Is it possible to enable face recognition and LPR per camera? I think mine is globally set currently. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, see the docs. Just disable it globally but enable it per-camera. https://docs-dev.frigate.video/configuration/license_plate_recognition/#configuration |
Beta Was this translation helpful? Give feedback.
-
|
Last issue "I think" I have the following set in my config: I have tried removing the above but I have old hardware and removing it makes no difference, error message is different but still causes ffmpeg to restart. This I believe worked in 0.16. I get the following in the logs |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I used the go2rRTC suggestion for the recording stream for front_door. This has removed all errors from the frigate side relating to ffmpeg. I am not sure if go2rtc is not showing the errors and what I have done is just a sticking plaster but CPU is now in a tight range of 30% +/1 5% usage, instead of watchdog (for ffmpeg) doing it's thing and CPU being in the 45% to 90% range. see screenshot below: from 14:00 is the change. my go2RTC config is now like this: I have just disabled "watchdog" just so I can see what issues watchdog is working around. This only issue i have now when "Watchdog" is disabled. Frigate add-on will not restart when I click restart, it stops the add-on and does not start it. I have to go to the add-on and select "start", frigate starts without an issue. here are the logs when I "restart" the frigate add-on: |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this looks normal now. The CPU usage increase is expected since you are doing transcoding with hardware acceleration to h264. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your help and patience. |
Beta Was this translation helpful? Give feedback.
-
|
Happy to help. I'll close this now but let us know if anything else comes up. |
Beta Was this translation helpful? Give feedback.
-
|
regarding the frigate restart issue, it is when i use the "frigate restart" option when i click the cog > Restart Frigate option in the Frigate UI. If I use the "Restart" option in the Frigate add-on it restarts without issue. |
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.
-
Describe the problem you are having
CPU is higher since upgrading from 0.17-beta1 to beta2. Is there way I can check when I updated to beta2 to be sure?
Beta Version
0.17.0-beta2
Issue Category
Performance / Stability
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output (if applicable)
No response
Install method
Home Assistant Add-on
docker-compose file or Docker CLI command
N/AOperating system
Home Assistant OS
CPU / GPU / Hardware
No response
Screenshots
Steps to reproduce
No response
Any other information that may be helpful
It may not be due to installing beta2 but can't see where to find date it was updated. It could have been a config change in frigate. Thanks.
Beta Was this translation helpful? Give feedback.
All reactions