Use in-memory index to rebuild index in prune

This commit is contained in:
Alexander Weiss authored and Alexander Neumann committed 2020-11-06 20:23:30 +01:00
1 parent 38cc4393f6
commit fd33030556
4 files changed
+38 -14

No files matched your search

+4
View File
@@ -3,6 +3,8 @@ Enhancement: Improve pruning performance and make pruning more customizable
The `prune` command is now much faster. This is especially the case for remote
repositories or repositories with not much data to remove.
Also the memory usage of the `prune` command is now reduced.
Restic used to rebuild the index from scratch after pruning. This is now
changed and the index rebuilding uses the information already known by `prune`.
By default, the `prune` command no longer removes all unused data. This
behavior can be fine-tuned by new options, like the acceptable amount of unused space or
@@ -14,9 +16,11 @@ also shows what `prune` would do.
Fixes several open issues, e.g.:
https://github.com/restic/restic/issues/1140
https://github.com/restic/restic/issues/1599
https://github.com/restic/restic/issues/1985
https://github.com/restic/restic/issues/2112
https://github.com/restic/restic/issues/2227
https://github.com/restic/restic/issues/2305
https://github.com/restic/restic/pull/2718
https://github.com/restic/restic/pull/2842