You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It feels like in the Repo settings page "Stats policy" is missing, like prune and check currently does. Seems natural to generate these stats on a daily basis for most users, making the "Stats" tab more useful when it has consistent data to display.
The text was updated successfully, but these errors were encountered:
Hmm, I'm a bit opinionated that stats shouldn't be scheduled other than after a prune operation runs (which is how it's done today).
This is because after a prune is the only time that a repo's size can be expected to be somewhat consistent. Restic will have just dropped extraneous data from the repo etc. Otherwise you should expect to see a fairly spiky chart depending on how much churn there is in your dataset. The second concern is that stats operations are surprisingly expensive: they do a full traversal of the repo's index.
Open to other opinions, but I don't see a very good use case for scheduled stats separately from prune.
Ah, I was not aware that was the case. As I had scheduled prune to only run once a week, so my new setup looked like it did not calculate stats first few days.
New suggestion: Include some info that it works what way, for example
In my scenario I only use Backrest as a UI/view on top of a series of restic repos I manage externally. All backups, forgetting and pruning is done outside of Backrest. But it would be nice to view the repo stats in Backrest, so I personally would be keen for a periodic "Compute Stats Policy" or the like.
It is mentioned briefly in #536.
It feels like in the Repo settings page "Stats policy" is missing, like
prune
andcheck
currently does. Seems natural to generate these stats on a daily basis for most users, making the "Stats" tab more useful when it has consistent data to display.The text was updated successfully, but these errors were encountered: