From 7d39b1bfe853be8102bba6c4d18f8dfa5fa3ce7d Mon Sep 17 00:00:00 2001 From: Patrick Wolf Date: Mon, 2 Jun 2025 14:40:04 -0400 Subject: [PATCH] Update 047_tuning_backup_parameters.rst - local backend (#5355) users would find it helpful to know how to adjust the "local" backend and they might not get the idea that the local backend is just called local... which in turn leads them to think restic is slow as they can't adjust away from 2 threads for restore and backup. --- doc/047_tuning_backup_parameters.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/047_tuning_backup_parameters.rst b/doc/047_tuning_backup_parameters.rst index a1f0eb02d..1f2292986 100644 --- a/doc/047_tuning_backup_parameters.rst +++ b/doc/047_tuning_backup_parameters.rst @@ -34,11 +34,12 @@ Backend Connections Restic uses a global limit for the number of concurrent connections to a backend. This limit can be configured using ``-o .connections=5``, for example for -the REST backend the parameter would be ``-o rest.connections=5``. By default restic uses -``5`` connections for each backend, except for the local backend which uses a limit of ``2``. -The defaults should work well in most cases. For high-latency backends it can be beneficial -to increase the number of connections. Please be aware that this increases the resource -consumption of restic and that a too high connection count *will degrade performance*. +the REST backend the parameter would be ``-o rest.connections=5`` or for the local backend +``-o local.connections=2``. By default restic uses ``5`` connections for each backend, +except for the local backend which uses a limit of ``2``. The defaults should work well in +most cases. For high-latency backends it can be beneficial to increase the number of +connections. Please be aware that this increases the resource consumption of restic and +that a too high connection count *will degrade performance*. CPU Usage