Closed KCH0000 closed 1 year ago
So it looks like you used 0.13 and then went back? that of course means the database is corrupt, like it shows in the logs. It is not clear what version you are referring to
So it looks like you used 0.13 and then went back? that of course means the database is corrupt, like it shows in the logs. It is not clear what version you are referring to
yes, I tried to roll back the version, but it didn't change the situation. Now I have returned to the latest version and updated the issue
Okay then this is a duplicate of https://github.com/blakeblackshear/frigate/issues/6861 and is related to motion settings being too sensitive which the next dev image should fix
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
In the latest update, frigate uses a lot of CPU. hardware acceleration for ffmpeg works fine, but the detector is high cpu usage. Сhanging the resolution of the image does not change the load on the processor
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 Compose
Coral version
USB
Any other information that may be helpful
OS: Ubuntu server 22.04.2 LTS
Docker version 20.10.12, build e91ed57