diff options
| author | Ahmad Sherif <me@ahmadsherif.com> | 2016-09-01 09:08:25 +0200 |
|---|---|---|
| committer | Ahmad Sherif <me@ahmadsherif.com> | 2016-09-02 11:11:37 +0200 |
| commit | a3828abb63306967c8e2d1c3602b8b7d953b74a0 (patch) | |
| tree | 87d698f0e21830bea071efdfe573a33992215adb | |
| parent | 619b350279c6e3a987cefce935fdaf7ab13632ff (diff) | |
| download | gitlab-ce-a3828abb63306967c8e2d1c3602b8b7d953b74a0.tar.gz | |
Change minimum Unicorns required to two
| -rw-r--r-- | doc/install/requirements.md | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md index b499d3422d1..04907249f5c 100644 --- a/doc/install/requirements.md +++ b/doc/install/requirements.md @@ -114,9 +114,7 @@ For most instances we recommend using: CPU cores + 1 = unicorn workers. So for a machine with 2 cores, 3 unicorn workers is ideal. For all machines that have 2GB and up we recommend a minimum of three unicorn workers. -If you have a 1GB machine with a magnetic (non-SSD) swap drive we recommend to configure only one Unicorn worker to prevent excessive swapping. -With one Unicorn worker only git over ssh access will work because the git over HTTP access requires two running workers (one worker to receive the user request and one worker for the authorization check). -If you have a 1GB machine with a SSD drive you can use two Unicorn workers, this will allow HTTP access although it will be slow due to swapping. +If you have a 1GB machine we recommend to configure only two Unicorn worker to prevent excessive swapping. To change the Unicorn workers when you have the Omnibus package please see [the Unicorn settings in the Omnibus GitLab documentation](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/unicorn.md#unicorn-settings). |