Nev
November 1, 2021, 6:30pm
2
Yes there is. But not in the release binaries. You either need to make changes to the code, as detailed by @fd0 here:
No, not easily. And I’m very reluctant to exposing this as a user-configurable option. If you want to experiment with it though, it’s easy to change in the source code here:
You can try setting minPackSize to something much larger than the default, like 64MiB (or even 256MiB), and try that. I think restic will cope just fine with larger packs, but I haven’t tried it in a long time. So please report back!
or make a version with a PR that adds this as an option, such as this one (–min-packsize):
restic:master ← metalsp0rk:min-packsize
opened 09:35PM - 24 May 20 UTC
<!--
Thank you very much for contributing code or documentation to restic! Plea… se
fill out the following questions to make it easier for us to review your
changes.
You do not need to check all the boxes below all at once, feel free to take
your time and add more commits. If you're done and ready for review, please
check the last box.
-->
What is the purpose of this change? What does it change?
--------------------------------------------------------
Would like to add the following in order to tune restic rather than hardcoding it.
--min-packsize
--file-read-concurrency
Was the change discussed in an issue or in the forum before?
------------------------------------------------------------
https://forum.restic.net/t/control-the-minimal-pack-files-size/617
Closes #2291
Checklist
---------
- [x] I have read the [Contribution Guidelines](https://github.com/restic/restic/blob/master/CONTRIBUTING.md#providing-patches)
- [x] I have enabled [maintainer edits for this PR](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
- [x] I have added tests for all changes in this PR
- [x] I have added documentation for the changes (in the manual)
- [x] There's a new file in `changelog/unreleased/` that describes the changes for our users (template [here](https://github.com/restic/restic/blob/master/changelog/TEMPLATE))
- [x] I have run `gofmt` on the code in all commits
- [x] All commit messages are formatted in the same style as [the other commits in the repo](https://github.com/restic/restic/blob/master/CONTRIBUTING.md#git-commits)
- [x] I'm done, this Pull Request is ready for review
I go the manual-edit route, and make my own executable every couple of releases (128Mb works great for me). If you’re not comfortable with that approach, you probably need to look for a different backup solution (for example, Borg defaults to 500Mb I believe).
The evidence for the need for this in a release version continues to grow broken record
1 Like
(sorry if I’m starting to sound like a broken record 
)