jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-22 11:26:57 -05:00
Code Issues Projects Releases Wiki Activity

State minimum hardware requirements for GHES Actions (#25230)

Browse Source
This commit is contained in:
Sarah Edwards
2022-02-15 12:08:42 -08:00
committed by GitHub
parent 6be25a9155
commit 1c1dd28195
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
View File

@@ -31,7 +31,7 @@ This article explains how site administrators can configure {% data variables.pr
{% data reusables.actions.migrating-enterprise %}
## Review hardware considerations
## Review hardware requirements
{% ifversion ghes = 3.0 %}
@@ -45,7 +45,7 @@ This article explains how site administrators can configure {% data variables.pr
{%- ifversion ghes < 3.2 %}
The CPU and memory resources available to {% data variables.product.product_location %} determine the maximum job throughput for {% data variables.product.prodname_actions %}.
The CPU and memory resources available to {% data variables.product.product_location %} determine the maximum job throughput for {% data variables.product.prodname_actions %}. {% data reusables.actions.minimum-hardware %}
Internal testing at {% data variables.product.company_short %} demonstrated the following maximum throughput for {% data variables.product.prodname_ghe_server %} instances with a range of CPU and memory configurations. You may see different throughput depending on the overall levels of activity on your instance.
@@ -53,7 +53,7 @@ Internal testing at {% data variables.product.company_short %} demonstrated the
{%- ifversion ghes > 3.1 %}
The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss.
The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %}
The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: