Преглед на файлове

Better formatting of CPU usage documentation

This is now displayed as a list, with bold fonts for each bullet.
Refers https://github.com/borgbackup/borg/issues/3554
Rémi Oudin преди 7 години
родител
ревизия
fe807046b4
променени са 1 файла, в които са добавени 6 реда и са изтрити 6 реда
  1. 6 6
      docs/usage_general.rst.inc

+ 6 - 6
docs/usage_general.rst.inc

@@ -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)
-    chunks cache sync: quite heavy on CPU, doing lots of hashtable operations.
-    borg extract: crypto, decompression (medium to high CPU usage)
-    borg check: similar to extract, but depends on options given.
-    borg prune / borg delete archive: low to medium CPU usage
-    borg delete repo: done on the server
+    - **borg create:** does chunking, hashing, compression, crypto (high CPU usage)
+    - **chunks cache sync:** quite heavy on CPU, doing lots of hashtable operations.
+    - **borg extract:** crypto, decompression (medium to high CPU usage)
+    - **borg check:** similar to extract, but depends on options given.
+    - **borg prune / borg delete archive:** low to medium CPU usage
+    - **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