What are the hardware requirements considerations for GitHub Enterprise Server sizing?
Select an answer to reveal the explanation.
Short Explanation and Infographic
GHES sizing isn't one-size-fits-all. GitHub publishes sizing guidelines based on user count and load. A 100-user instance needs much less than a 10,000-user instance. CPU, RAM, storage I/O, and disk space all scale with usage — especially if you're running Actions.
Full explanation below image
Full Explanation
GitHub Enterprise Server hardware requirements are usage-dependent and scale with: (1) Number of active users — more users require more RAM and CPU. (2) Repository count and size — large monorepos require significant storage. (3) GitHub Actions usage — CI/CD workloads require additional CPU, and actions cache storage requires significant disk. (4) Network I/O — git clone/push operations are bandwidth-intensive. GitHub's sizing recommendations (in the documentation) provide starting points: small (up to 3,000 users), medium (up to 8,000 users), large (up to 30,000 users) with specific CPU, RAM, and storage requirements for each tier. For example, a 3,000-user instance typically requires 8 vCPU, 64 GB RAM, and 500 GB primary storage (SSD). Running Actions significantly increases storage needs due to caching.