diff options
| author | Andrew Winata <awinata@gitlab.com> | 2019-06-03 01:01:12 +0000 |
|---|---|---|
| committer | Andrew Winata <awinata@gitlab.com> | 2019-06-03 01:01:12 +0000 |
| commit | 7f5d4e72a7d5ce0451aa09d1dc90d17eef5cc65c (patch) | |
| tree | f9e64105e9cfae8951082323d7e46fdaf1d0f570 | |
| parent | a33bcbe5ec998cd7556456272ffcf55c573fe00b (diff) | |
| download | gitlab-ce-Docs-add-info-about-runner-server-requirements.tar.gz | |
Reshuffle, reference & emphasis on runner requirement.Docs-add-info-about-runner-server-requirements
| -rw-r--r-- | doc/install/requirements.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md index efd4345af97..7e9541833f1 100644 --- a/doc/install/requirements.md +++ b/doc/install/requirements.md @@ -201,20 +201,20 @@ 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. -- Executors you configured on GitLab Runner. +- Job concurrency settings. -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: +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. |