I just upgraded from restic 0.8.3 to 0.9.5.
I’m running Restic on a Debian Stretch host.
No matter whether I’m doing a recurring full system backup (with several file exclusions) or a backup of my Nextcloud over WebDAV, the backup (backup target is a SFTP server within the same datacenter, Gigabit connection) takes ways longer with 0.9.5 than it did with 0.8.3
Full System Backup (around 100 GB, 186339 files):
0.8.3: 8 minutes
0.9.5: 2 hours 50 minutes
Any ideas whether restic changed the way how it discovers files? (I just did a brief look into the changelog but didn’t find any eye-catching change)
Any idea how I can trace down which component is responsible for that?
Enhancement #549: Rework archiver code
The core archiver code and the complementary code for the backup command was rewritten completely. This resolves very annoying issues such as 549. The first backup with this release of restic will likely result in all files being re-read locally, so it will take a lot longer. The next backup after that will be fast again.
[…]
39 minutes is way too long to scan 15k files. On 1 of my systems with spinning disks and restic 0.9.5 it takes 18 seconds to scan 176k files. Maybe you can do some benchmarking to see if this delay is caused by hardware.