Default schedule for maintaince seem too agressive?

I run my backups every 12 hours.
However, it seems like “Periodic maintenance” is run every hour.
It seems like it’s redundant and wasteful to run maintenance so often, don’t you think? Nothing changed in my repositories between those 12 hours.
With local backups that’s just wasted resources, but with online backups like B2 or S3 it actually costs money in API requests.

Shouldn’t maintenance jobs schedule automatically be adjusted in proportion to the actual backup jobs?

Hello, I think that you could set interval with maintenance set command.

Yes, it can be manually adjusted, but I’m talking about sane defaults…

But even if manually adjusting that schedule, the documentation doesn’t instructs on the recommended intervals. How often should it be run? Once between each backup? Twice? Once every 10 backups? Etc.

1 Like