cpu requests

Signed-off-by: Shruti Deshpande <[email protected]>

Author: shdeshpa07

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

@@ -9,9 +9,13 @@ Testing shows that increasing `NodeAgent` CPU can significantly improve backup a
 
 [IMPORTANT]
 ====
-Customers can tune their OpenShift environments based on the their analysis and preference.  Red Hat does not recommend using CPU limits in environments where Kopia is required. 
+You can tune your {product-short} environment based on your performance analysis and preference. It is not recommended to use CPU limits in workloads where you use Kopia for file system backups.
 
-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.
+If you do not use CPU limits on the pods, then the pods can use excess CPU when available. Whereas, if you specify CPU limits, there is a chance that pods may get throttled, if they exceed their limit. Therefore, using CPU limits on the pods is considered as an anti-pattern.
+
+Ensure that you are accurately specifying CPU requests, so that pods can take advantage of excess CPU. Resource allocation is guaranteed based on CPU requests rather than CPU limits.
+
+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.
 ====
 
 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.