Merge pull request #35417 from github/repo-sync

Repo sync
github · Nov 25, 2024 · e27b251 · e27b251
2 parents 5c9b0b1 + 4d37612
commit e27b251
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 3 deletions.
diff --git a/...ub-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md b/...ub-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
@@ -26,6 +26,14 @@ shortTitle: Install on Hyper-V
 
 {% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
 
+## Should I use VMotion?
+
+VMotion can be exceptionally helpful for general resource management, however the impact to the guest instance can be significant. With larger {% data variables.product.prodname_ghe_server %} instances (8 CPU/64 GB RAM and above), a VMotion event may result in a full outage of the {% data variables.product.prodname_ghe_server %} to end users as a result of dramatically reduced CPU, RAM, and storage IOPS. With this in mind, {% data variables.product.prodname_ghe_server %} should be considered a "highly latency sensitive" application.
+
+For large(r) deployments on VMWare that have Distributed Resource Scheduler (DRS) enabled, we would recommend configuring a VM-to-Host affinity rule for your {% data variables.product.prodname_ghe_server %} to try and keep the virtual appliance on a single host. If a migration with VMotion is required, we'd recommend considering this a "planned outage", and placing {% data variables.product.prodname_ghe_server %} into maintenance mode until the migration is complete.
+
+We also recommend that the ESXi Power Management Setting be configured to "High Performance". We have seen cases where overall system performance can be negatively impacted if this is left at "Balanced".
+
 ## Downloading the {% data variables.product.prodname_ghe_server %} image
 
 {% data reusables.enterprise_installation.download-license %}

diff --git a/data/reusables/actions/more-resources-for-ghes.md b/data/reusables/actions/more-resources-for-ghes.md
@@ -1,8 +1,8 @@
 If you plan to enable {% data variables.product.prodname_actions %} or {% data variables.product.prodname_GH_advanced_security %} for the users of your instance, more resources are required.
 
-* {% data variables.product.prodname_actions %} - increase CPU and memory by 25%
-* {% data variables.product.prodname_GH_advanced_security %} - increase CPU and memory by 15%
+* {% data variables.product.prodname_actions %} - increase both CPU and memory by at least 25%
+* {% data variables.product.prodname_GH_advanced_security %} - increase both CPU and memory by at least 25%
 
-These adjustments should be applied to the base requirements for each user tier.
+These adjustments should be applied to the base requirements for each user tier. We recommend monitoring all changes to your resources, as further increases may be needed.
 
 For more information about these requirements, see "[AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."