Closed BlackRapsbeere closed 8 months ago
for starts I would recommend using ffmpeg presets for input_args and record_args and I would also not recommend overriding detect or global args, you are removing args from the defaults that are there to reduce cpu usage
As far as I can see from the frigate-code on github, I did actually not change anything for the mentioned camera. All the setting are as they would be in the preset. I just rather see the settings explicitly. I added the threads now and will see how it is going tomorrow
that is incorrect, the global args and detect args are outdated. Also, not using presets means that when we make additional improvements to the args they will not be automatically applied.
I doubt this affects CPU usage, but your max_ratio setting for most of your objects is astronomical. Is there a reason? Are those actually the default settings?
Are those actually the default settings?
Those are the default values
Are those actually the default settings?
Those are the default values
Gotcha, I thought they might be.
So I got rid of the ffmpeg settings and returned to the presets. I also deleted the go2rtc settings for ffmpeg. the cpu usage of that one camera stays way to high around 100% Any other ideas?
would want to check the debug live view with motion and object boxes enabled and see what is going on
I set the config as recommended. Nothing really changed except the dual-thread usage kind of smoothes things out and makes it more reliable. So I tried to watch the debug screens a little while. As soon as there is something moving in the image the CPU-usage goes up to about 50%. The debug screen show one or two "regions" covering most of the image. In this regions nothing is actually moving. There are 4 cars in 3 different drive-ways and one front door of a house is detected as a person. The region then stays there for about a minute, I guess, and then disapears. When there is no region shown, the CPU usage drops to about 1% Any further ideas?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the problem you are having
Hi everyone. I am kind of concerned about the CPU usage of my detect process for the doorbell. Please see attached screenshot. I have set the detect fps to 10 and a coral via M.2. I do not understand how there is such high CPU usage. It is an Intel Xeon E3-1245 v5 and I hope the 158% are CPU-time in thousand miliseconds. The Intel QSV is working as indicated by the usage. Also the TPU seems to work. Where is the fault? Appreciate all the ideas and help! Regards
Version
0.12.1-367d724
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
Operating system
Other Linux
Install method
Docker CLI
Coral version
M.2
Any other information that may be helpful
No response