Update recommendations for adjusting resources on GHES when Actions or Codespaces is enabled. #35281
Open
1 task done
Labels
content
This issue or pull request belongs to the Docs Content team
enterprise
Content relating to GitHub Enterprise
Code of Conduct
What article on docs.github.com is affected?
Hello.
The document that would be affected would be this one :
https://docs.github.com/en/[email protected]/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform
And all it's variants for other platforms (VMWare, Azure, AWS, etc...)
What part(s) of the article would you like to see updated?
The part that I would like to see updated is the part where we say :
I believe the documentation should be changed here because it implies that a customer who will simply add more resources will be fine in all cases.
I believe that the customers here should first make the change in terms of resources (CPU and Memory), but once this is done, they should monitor the appliance for resource utilisation, and make appropriate changes as required.
This is also documented in another article where we ask customers to first monitor their appliance in order to establish a baseline in terms of resource utilisation, and make the necessary adjustments after.
That document implies that the baseline should be around 60% of all available resources (this assumption is made based on the recommended threshold for alerts).
The document in question is this one : https://docs.github.com/en/[email protected]/admin/monitoring-and-managing-your-instance/monitoring-your-instance/recommended-alert-thresholds#monitoring-cpu-and-load-average-usage
This is the reason why I would like to see this changed.
The change I would like to see would be something along the lines of :
I do expect that the outcome will be that we will have less customer running GHES on resource-constrained environment, leading to a better user/customer experience, better satisfaction, and overall less support ticket for this type of issues.
Additional information
No response
The text was updated successfully, but these errors were encountered: