From 2bd66498138498c39468a7584947bc7a0a9ee968 Mon Sep 17 00:00:00 2001 From: DoS007 Date: Sun, 16 Nov 2025 13:48:56 +0100 Subject: [PATCH] docs: add info about ssd wear in backend connections (#5496) --------- Co-authored-by: Michael Eischer --- doc/047_tuning_backup_parameters.rst | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/doc/047_tuning_backup_parameters.rst b/doc/047_tuning_backup_parameters.rst index 5131aa0ab..f0510a57d 100644 --- a/doc/047_tuning_backup_parameters.rst +++ b/doc/047_tuning_backup_parameters.rst @@ -34,12 +34,14 @@ 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`` or for the local backend -``-o local.connections=2``. By default restic uses ``5`` connections for each backend, +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*. +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*. This can also result in longer +upload times for single temporary packs, which can lead to more disk wear on SSDs (see +:ref:`Pack Size`). CPU Usage @@ -85,6 +87,8 @@ by reading more files in parallel. You can specify the concurrency of file reads the ``backup`` command. +.. Pack Size: + Pack Size =========