New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Support]: very slow startup time #9424
Comments
Does this happen every time? |
Unfortunately no. I haven't been able to pinpoint a trigger. |
Judging by the logs, either something in Looking at the former, it will perform vacuuming (https://www.sqlite.org/lang_vacuum.html) on the sqlite DB on startup if it hasn't happened in the last two weeks. This could potentially cause a delay, if you had a large Frigate DB. What's the output of Otherwise, sharing the output of |
I'm currently managing 3 frigate setups and they all have very similar configuration (proxmox/lxc/coral/docker) with the exception of the amount of cameras and brands on each setup... Each setup crashes due to a memory leak at some point that I have not been able to pinpoint but something that's has become obvious is the time that takes to boot when the database has store many new events and no new requests has been sent to "http://frigate_server_ip:5000/events" apparently this request keeps the sqlite cache current allowing normal boot times, shorter vacuum times and preventing memory leaks. I'm making reference to my post where I wonder if support to a more robust database is in the roadmap here although seems like that's not an option. The only way I've been able to keep normal frigate's boot time (due to long vacuum process or sqlite recovery process) is by running a cron job every few minutes to "http://frigate_server_ip:5000/event" . The time between request depends on how often new events are being created . This is not ideal and this should not happen to begin with... but I have not been able to properly debug this 2 problems as the server becomes inaccessible due to high cpu/memory usage or while the server is booting as the frigate container is not fully up and seems like this is not happening to anyone in the frigate dev team. |
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
frigate startup is taking a very long time. from a
docker-compose up -d
to frigate actually running takes about 5 minutesVersion
0.13.0-c35c7da
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
No response
Operating system
Other Linux
Install method
Docker Compose
Coral version
PCIe
Network connection
Wired
Camera make and model
N/A
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: