Skip to content
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

Configuration: expire_interval for snapshots #14002

Open
c4talyst opened this issue Sep 27, 2024 · 8 comments
Open

Configuration: expire_interval for snapshots #14002

c4talyst opened this issue Sep 27, 2024 · 8 comments
Labels
enhancement New feature or request pinned

Comments

@c4talyst
Copy link

Describe what you are trying to accomplish and why in non technical terms
I want to be able to configure the expire_interval of snapshots so that Frigate can reduce disk activity.

Describe the solution you'd like
In configuration, there is a expire_interval for record; there is no such setting for snapshots. If I could set the interval for snapshots I could reduce disk activity.

The default appears to be 300 seconds (every 5 minutes)
https://github.com/blakeblackshear/frigate/blob/master/frigate/storage.py#L213

Describe alternatives you've considered
I could move snapshots/clips to a different disk (e.g. a SSD) to prevent disks from spinning

Additional context
Debugging this as per #10611 (comment) and using inotifywait to identify what was causing the disk to spin; command below:

inotifywait -m -r /mnt/disk2/cctv | awk '{ print strftime("[%Y-%m-%d %H:%M:%S]"), $0; fflush() }'
@c4talyst c4talyst added the enhancement New feature or request label Sep 27, 2024
@jmot205
Copy link

jmot205 commented Oct 27, 2024

This would be a great addition so we can cut down on IO and let HDDs stay spun down for much longer

@NickM-27
Copy link
Collaborator

To be clear you can already do this by mapping the clips directory separate from recordings

@jmot205
Copy link

jmot205 commented Oct 27, 2024

Yeah that's definitely an option I've been considering, it's just that HDD space is at less of a premium than the cache's SSD for my system currently.

@c4talyst
Copy link
Author

To be clear you can already do this by mapping the clips directory separate from recordings

Correct - and as per the description of the issue - this is the alternative currently in use to reduce spinning disk activity. However, having it configurable similar to recording would be the goal, as @jmot205 mentions, SSD space is a premium.

Thanks for a great app

@WaffleMaster22
Copy link

To be clear you can already do this by mapping the clips directory separate from recordings

How would I do this? I can't find anything about that in the docs. I added a new path to the docker container but idk what to put in the config. 'path: /clips/path' does not work under snapshots

@NickM-27
Copy link
Collaborator

NickM-27 commented Nov 7, 2024

you don't define anything in the frigate config.

@WaffleMaster22
Copy link

you don't define anything in the frigate config.

Oh okay, the way unraid has the paths set up by default made 'media' all one folder with clips, recordings, and exports. But I figured out how to separate it, thanks

@c4talyst
Copy link
Author

c4talyst commented Nov 8, 2024

you don't define anything in the frigate config.

Oh okay, the way unraid has the paths set up by default made 'media' all one folder with clips, recordings, and exports. But I figured out how to separate it, thanks

Can you share, to help the next person who stumbles across this post. TIA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pinned
Projects
None yet
Development

No branches or pull requests

4 participants