Michael Eischer

> In my case: 500k files, 1.4 TB in total. Peak memory usage: 220 GiB. I have never seen memory usage from restic that is even close to that. For...

> In my case: 500k files, 1.4 TB in total. Peak memory usage: 220 GiB... Here is the illustration of four overnight attempts @mirekphd After thinking about this a bit...

The MinIO S3 library by default uses a multipart size of 16MB. You'll probably have to patch restic to increase the limit: ```diff diff --git a/internal/backend/s3/s3.go b/internal/backend/s3/s3.go index 1bdf2d795..c124329ae 100644...

This will be pretty easy to implement once #2913 is merged.

I've rebased the PR resolve the conflicts with #2913. > Maybe we need to approach this differently and just map / to _, then accept that tags/foo_bar holds snapshots labeled...

Some of the labels in the last sixth of your table seem to be broken. '1 default' in the SaveBlob column can't be right. Is VmPeak the same as maximum...

> In experiments using my naive PoC, the thread count was incredibly useful, especially when using either NVMe or a RAM disk as the temporary directory, and I was easily...

I mainly consider this to be a feature that could be useful for some users (I've never had that problem) but I haven't thought much about it, as I'm busy...

According to the documentation `mklink /d` creates a symbolic link to a directory. restic _always_ backs up symbolic links as symbolic links and _never_ follows them. What's a bit surprising...

So essentially the question is whether directory junctions should be treated like mount points on Unix systems or not. At least Go has decided that both symlink and junctions should...