Skip to content

Commit 7ee553f

Browse files
committed
remove cpu limit
Signed-off-by: Shruti Deshpande <[email protected]>
1 parent 7f8eed0 commit 7ee553f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

modules/oadp-backup-restore-for-large-usage.adoc

+4-4
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ Testing shows that increasing `NodeAgent` CPU can significantly improve backup a
99

1010
[IMPORTANT]
1111
====
12-
It is not recommended to use Kopia without limits in production environments on nodes running production workloads due to Kopia’s aggressive consumption of resources. However, running Kopia with limits that are too low results in CPU limiting and slow backups and restore situations. Testing showed that running Kopia with 20 cores and 32 Gi memory supported backup and restore operations of over 100 GB of data, multiple namespaces, or over 2000 pods in a single namespace.
13-
====
12+
It is not recommended to use Kopia without limits in production environments on nodes running production workloads due to Kopia’s aggressive consumption of resources. However, running Kopia with limits that are too low results in CPU limiting and slow backups and restore situations.
1413
15-
Testing detected no CPU limiting or memory saturation with these resource specifications.
14+
Testing showed that running Kopia with 20 cores and 32 Gi memory supported backup and restore operations of over 100 GB of data, multiple namespaces, or over 2000 pods in a single namespace. Testing detected no CPU limiting or memory saturation with these resource specifications.
15+
====
1616

1717
In some environments it may be necessary to adjust Ceph MDS pods resources to avoid pod restarts caused by resource saturation when default settings are used.
1818

19-
You can set these limits in Ceph MDS pods by following the procedure in https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.15/html/troubleshooting_openshift_data_foundation/changing-resources-for-the-openshift-data-foundation-components_rhodf#changing_the_cpu_and_memory_resources_on_the_rook_ceph_pods[Changing the CPU and memory resources on the rook-ceph pods].
19+
You can set the pods resources limits in Ceph MDS pods by following the procedure in https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.15/html/troubleshooting_openshift_data_foundation/changing-resources-for-the-openshift-data-foundation-components_rhodf#changing_the_cpu_and_memory_resources_on_the_rook_ceph_pods[Changing the CPU and memory resources on the rook-ceph pods].

0 commit comments

Comments
 (0)