Skip to content

Commit a78083e

Browse files
Andrew Winataeread
Andrew Winata
authored andcommitted
Mentioned executors type
Also another factor of consideration for runner server requirements.
1 parent b11dcd2 commit a78083e

File tree

1 file changed

+13
-2
lines changed

1 file changed

+13
-2
lines changed

doc/install/requirements.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -208,12 +208,23 @@ you decide to run GitLab Runner and the GitLab Rails application on the same
208208
machine.
209209

210210
It is also not safe to install everything on a single machine, because of the
211-
[security reasons](https://docs.gitlab.com/runner/security/)
212-
- especially when you plan to use shell executor with GitLab
211+
[security reasons](https://docs.gitlab.com/runner/security/), especially when you plan to use shell executor with GitLab
213212
Runner.
214213

215214
We recommend using a separate machine for each GitLab Runner, if you plan to
216215
use the CI features.
216+
The GitLab Runner server requirements depend on:
217+
218+
- The type of [executor](https://docs.gitlab.com/runner/executors/) you configured on GitLab Runner.
219+
- Resources required to run build jobs.
220+
- Job concurrency settings.
221+
222+
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.
223+
224+
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:
225+
226+
- 1vCPU.
227+
- 3.75GB of RAM.
217228

218229
## Supported web browsers
219230

0 commit comments

Comments
 (0)