docs: add info about ssd wear in backend connections (#5496)

---------

Co-authored-by: Michael Eischer <michael.eischer@fau.de>
This commit is contained in:
DoS007 2025-11-16 13:48:56 +01:00 committed by GitHub
parent 5b173d2206
commit 2bd6649813
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -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 <backend-name>.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
=========