From 360e7ef707d7af29c1de1c053b9c5c28fc24175e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 4 Jun 2026 16:30:38 +0000 Subject: [PATCH] Refine Kopia-only performance and maintenance docs --- site/content/docs/main/performance-guidance.md | 4 ++-- site/content/docs/main/repository-maintenance.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/site/content/docs/main/performance-guidance.md b/site/content/docs/main/performance-guidance.md index 42ea3ab9b..b1b1f1fab 100644 --- a/site/content/docs/main/performance-guidance.md +++ b/site/content/docs/main/performance-guidance.md @@ -83,7 +83,7 @@ Below we've done 6 groups of tests. For each single group of test, we used limit Recorded the metrics of time consumption, maximum CPU usage, maximum memory usage, and minio storage usage for node-agent daemonset. The metrics of Velero deployment are not included. -Compression is either disabled or not unavailable for both uploader. +Compression is disabled for testing purposes. ### Case 1: 4194304(4M) files, 2396745(2M) directories, 0B per file total 0B content #### result: @@ -144,5 +144,5 @@ Compression is either disabled or not unavailable for both uploader. ## Summary - With the same specification resources, Kopia uploader is less time-consuming when backup. -- Performance would be better if choosing Kopia uploader for the scenario in backup large mounts of data or massive small files. +- Kopia uploader performs well when backing up large amounts of data or massive small files. - It's better to set one reasonable resource configuration instead of the default depending on your scenario. With default configuration, it's easy to hit timeout or OOM in large-scale backups. diff --git a/site/content/docs/main/repository-maintenance.md b/site/content/docs/main/repository-maintenance.md index c8b8b225d..fb8a2d4fb 100644 --- a/site/content/docs/main/repository-maintenance.md +++ b/site/content/docs/main/repository-maintenance.md @@ -23,7 +23,7 @@ If there is a key value as `global` in the map, the key's value is applied to al The other keys in the map is the combination of three elements of a BackupRepository, because those three keys can identify a unique BackupRepository: * The namespace in which BackupRepository backs up volume data. * The BackupRepository referenced BackupStorageLocation's name. -* The BackupRepository's type. Current value is `kopia`. +* The BackupRepository's type. Possible value is `kopia`. If there is a key match with BackupRepository, the key's value is applied to the BackupRepository's maintenance jobs. By this way, it's possible to let user configure before the BackupRepository is created.