Michael Eischer 98709a4372 retry: reduce total number of retries ... Retries in restic try to solve two main problems: - retry a temporarily failed operation - tolerate temporary network interruptions The first problem only requires a few retries, whereas the last one benefits primarily from spreading the requests over a longer duration. Increasing the default multiplier and the initial interval works for both cases. The first few retries only take a few seconds, while later retries quickly reach the maximum interval of one minute. This ensures that the total number of retries issued by restic will remain at around 21 retries for a 15 minute period. As the concurrency in restic is bounded, retries drastically reduce the number of requests sent to a backend. This helps to prevent overloading the backend.		2024-05-24 20:24:02 +02:00
..
backend_retry_test.go	retry: ensure that there's always at least one retry	2024-05-24 20:24:02 +02:00
backend_retry.go	retry: reduce total number of retries	2024-05-24 20:24:02 +02:00
testing.go	Rename unused testing parameter to _	2023-05-18 21:17:53 +02:00