Updating known-issues-with-upgrades-to-your-instance.md for 3.11 and …

…above upgrades (#51191) Co-authored-by: Ryan Trauntvein <[email protected]> Co-authored-by: Rachael Rose Renk <[email protected]>
github · Jun 17, 2024 · 79825f2 · 79825f2
1 parent bb5c24d
commit 79825f2
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/...l-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance.md b/...l-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance.md
@@ -197,3 +197,9 @@ If you're affected by this problem, restore your {% data variables.product.prodn
 For more information about restoring from a failed upgrade, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#restoring-from-a-failed-upgrade)."
 
 {% endif %}
+{% ifversion ghes > 3.10 and ghes < 3.13 %}
+
+## Recommendations for server resources
+
+If your appliance averages more than 70% CPU utilization, {% data variables.product.company_short %} strongly recommends scaling up your server resources before upgrading to 3.11 or above. The new hardware or instance type should have more vCPUs to accommodate the additional load from new features and improvements included with the latest releases.
+{% endif %}