diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-03-18 20:02:30 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-03-18 20:02:30 +0000 |
| commit | 41fe97390ceddf945f3d967b8fdb3de4c66b7dea (patch) | |
| tree | 9c8d89a8624828992f06d892cd2f43818ff5dcc8 /doc/install/requirements.md | |
| parent | 0804d2dc31052fb45a1efecedc8e06ce9bc32862 (diff) | |
| download | gitlab-ce-41fe97390ceddf945f3d967b8fdb3de4c66b7dea.tar.gz | |
Add latest changes from gitlab-org/gitlab@14-9-stable-eev14.9.0-rc42
Diffstat (limited to 'doc/install/requirements.md')
| -rw-r--r-- | doc/install/requirements.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md index bce9702b032..11f623641c1 100644 --- a/doc/install/requirements.md +++ b/doc/install/requirements.md @@ -258,7 +258,7 @@ works. ### Puma per worker maximum memory By default, each Puma worker will be limited to 1024 MB of memory. -This setting [can be adjusted](../administration/operations/puma.md#puma-worker-killer) and should be considered +This setting [can be adjusted](../administration/operations/puma.md#change-the-memory-limit-setting) and should be considered if you need to increase the number of Puma workers. ## Redis and Sidekiq @@ -303,7 +303,7 @@ The GitLab Runner server requirements depend on: Since the nature of the jobs varies for each use case, you need to experiment by adjusting the job concurrency to get the optimum setting. -For reference, the [SaaS runners on Linux](../ci/runners/build_cloud/linux_build_cloud.md) +For reference, the [SaaS runners on Linux](../ci/runners/saas/linux_saas_runner.md) are configured so that a **single job** runs in a **single instance** with: - 1 vCPU. |