mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2025-01-03 13:45:31 +00:00
Code Issues Releases Wiki Activity

Better formatting of CPU usage documentation

Browse source 
This is now displayed as a list, with bold fonts for each bullet.
Refers https://github.com/borgbackup/borg/issues/3554
This commit is contained in:
Rémi Oudin 2018-01-30 16:27:54 +01:00
parent 26f1cd1486
commit 88972d7d81
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
docs/usage_general.rst.inc
View file

@ -306,12 +306,12 @@ all the resource usage occurs in that one process, so just add up client +
server to get the approximate resource usage. server to get the approximate resource usage.
CPU client: CPU client:
borg create: does chunking, hashing, compression, crypto (high CPU usage) - **borg create:** does chunking, hashing, compression, crypto (high CPU usage)
chunks cache sync: quite heavy on CPU, doing lots of hashtable operations. - **chunks cache sync:** quite heavy on CPU, doing lots of hashtable operations.
borg extract: crypto, decompression (medium to high CPU usage) - **borg extract:** crypto, decompression (medium to high CPU usage)
borg check: similar to extract, but depends on options given. - **borg check:** similar to extract, but depends on options given.
borg prune / borg delete archive: low to medium CPU usage - **borg prune / borg delete archive:** low to medium CPU usage
borg delete repo: done on the server - **borg delete repo:** done on the server
It won't go beyond 100% of 1 core as the code is currently single-threaded. It won't go beyond 100% of 1 core as the code is currently single-threaded.
Especially higher zlib and lzma compression levels use significant amounts Especially higher zlib and lzma compression levels use significant amounts
of CPU cycles. Crypto might be cheap on the CPU (if hardware accelerated) or of CPU cycles. Crypto might be cheap on the CPU (if hardware accelerated) or