aawsome

I finished working on all restic commands in the branch [optimize-large-dir](https://github.com/aawsome/restic/tree/optimize-large-dir). It seems that all commands I tested so far use less (some much less) memory and are faster with...

> are there any news on that? I have a directory with 2,113,804 files and 11,1TB to backup and the oom_reaper kills the process lately every day :( I am...

I don't want to argument that restic doesn't have a problem here - it definitively uses much more memory than needed and creates huge tree blobs in this case. And...

> While I definitely think this is a great improvement, and I want to implement it, there seems to be a complete rework of the prune functionality, which will likely...

> Unless I've missed something (or a backend is horribly memory inefficient), restic shouldn't load full pack files into memory. So where does this change actually reduce memory usage? In...

I just discovered that there is might be an issue with this PR and the `restore` command. If I understood `filerestorer.go` correctly, it holds (up to) the full pack contents...

> I second that it would be nice to be able to configure this once at the repository level, in addition to the existing command-line and environment variable additions. I...

About memory usage (or general ressource usage), I think there are basically two possible points to consider: 1. Some parts of the the restic code read (almost) a complete pack...

> If I have a repository with the default value of 4 and I want to switch to a higher value of 32. Can I run a prune to repack...

> There has already been some discussion on such an option in #2714. Thanks for the hint! I added this to in the description and adapted the changelog file.