mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-08-19 21:56:12 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Refine Kopia-only performance and maintenance docs

Browse Source
This commit is contained in:
copilot-swe-agent[bot]
2026-06-04 16:30:38 +00:00
committed by GitHub
parent 9331bffa7d
commit 360e7ef707
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
site/content/docs/main/performance-guidance.md
+2 -2
View File
@@ -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.
site/content/docs/main/repository-maintenance.md
+1 -1
View File
@@ -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.