|
|
|
|
|
|
by chillfox
17 days ago
|
|
|
Thanks for building this, I am just about to give it ago with my self-hosted Garage cluster. Does running `stat` against a file require pulling the whole file from s3, or can that be handled by the metadata? Do you know what backup performance is like for something like borg/borgmatic or restic, especially on follow up runs where most files are just checked. Is there any particular Redis/Valkey config you recommend when using it for `conditional_put`, or just default config? Is there any chance for NFSv4 support? |
|
|
stat doesn’t pull the file contents from S3; it only accesses the metadata tree, which is usually cached.
I haven’t benchmarked Borg or Restic specifically. Sequential writes can comfortably reach several Gbit/s. For follow-up runs, if they only stat unchanged files, that should stay entirely in metadata.
The default Redis/Valkey configuration should work fine for conditional_put. NFSv4 is unlikely for now. It would add a lot of surface area, and I’m pretty happy with where the 9P extensions are today.