diff options
| author | Andrew Winata <awinata@gitlab.com> | 2019-06-05 04:13:52 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-06-05 04:13:52 +0000 |
| commit | a78083eef2c808dccf6750bd25ad180445717c10 (patch) | |
| tree | f258ab1c6092df0511467353d8bc471995c4ea2d | |
| parent | b11dcd25a8a2e62f9b68646f17a11f08f50237bc (diff) | |
| download | gitlab-ce-a78083eef2c808dccf6750bd25ad180445717c10.tar.gz | |
Mentioned executors type
Also another factor of consideration for
runner server requirements.
| -rw-r--r-- | doc/install/requirements.md | 15 |
1 files changed, 13 insertions, 2 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md index a0e719952b4..107d48fb90c 100644 --- a/doc/install/requirements.md +++ b/doc/install/requirements.md @@ -208,12 +208,23 @@ you decide to run GitLab Runner and the GitLab Rails application on the same machine. It is also not safe to install everything on a single machine, because of the -[security reasons](https://docs.gitlab.com/runner/security/) -- especially when you plan to use shell executor with GitLab +[security reasons](https://docs.gitlab.com/runner/security/), especially when you plan to use shell executor with GitLab Runner. We recommend using a separate machine for each GitLab Runner, if you plan to use the CI features. +The GitLab Runner server requirements depend on: + +- The type of [executor](https://docs.gitlab.com/runner/executors/) you configured on GitLab Runner. +- Resources required to run build jobs. +- Job concurrency settings. + +Since the nature of the jobs varies for each use case, you will need to experiment by adjusting the job concurrency to get the optimum setting. + +For reference, GitLab.com's [auto-scaling shared runner](../user/gitlab_com/index.md#shared-runners) is configured so that a **single job** will run in a **single instance** with: + +- 1vCPU. +- 3.75GB of RAM. ## Supported web browsers |