dgtlmoon/changedetection.io

Backups skyrocketing in size

Closed this issue · 5 comments

Describe the bug
My last cd.io backup from less then a month ago is 60 MB but yesterday's one is over 200 MB.

Version
v0.47.03

To Reproduce

Steps to reproduce the behavior:

  1. Go back in time and do a backup a month ago.
  2. Go back to today and do a backup.
  3. Observe the size difference and raise an eyebrow.

Expected behavior
Backup size grows roughly linearly with number of watches.

Desktop (please complete the following information):

  • OS: Linux
  • Browser: Firefox
  • Enviroment: Docker

Additional context
I have over 400 watches, a month ago I might have had 380-ish. Not enough to explain the difference. My guess is it's because of the new (I think it's new) feature allowing you to compare and show not only differences between current and last check but also a number of checks in the past. While it might be useful to some, it can let the data folder (and backup consequently) grow like cancer.

I suggest a global option to let user choose max number of diffs to keep.

Can you make a new issue? this is a lot of text when it all just comes down "I suggest a global option to let user choose max number of diffs to keep."

thanks

duplicate #2216

I see this more as a Bug report then Feature request. What I suggested was just one way to solve this without sacrificing multiple diffs for people who need them.

#2216 talks about only needing binary change/no-change option. Not about limiting number of diffs to keep.

In progress - #2722

Update: Problem which is perhaps tied to this that I have now is that Backup itself doesn't work. Clicking Backup option produces few minutes of loading of the cd.io tab and then crash of the tab (maybe tied to the cd.io data size increase?)