summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Bodenmiller <bbodenmiller@hotmail.com>2019-05-11 09:42:08 +0000
committerBen Bodenmiller <bbodenmiller@gmail.com>2019-06-09 01:14:22 -0700
commita28ad5cabc232034d4eb17c69a07a6ff62e41c58 (patch)
treea15efa8a62f07c644d48929340ddff5e284bc23b
parent513fa60310e5b5d8dbdf81daf0c6ae7e506b4d8b (diff)
downloadgitlab-ce-patch-55.tar.gz
Improve details about acceptable number of unicorn workerspatch-55
-rw-r--r--doc/install/requirements.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index f6a52205a0e..d633b434f7b 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -161,14 +161,14 @@ CREATE EXTENSION postgres_fdw;
## Unicorn Workers
-It's possible to increase the amount of unicorn workers and this will usually help to reduce the response time of the applications and increase the ability to handle parallel requests.
-
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 we recommend to configure only two Unicorn workers to prevent excessive swapping.
+As long as you have enough available CPU and memory capacity, it's okay to increase the number of unicorn workers and this will usually help to reduce the response time of the applications and increase the ability to handle parallel requests.
+
To change the Unicorn workers when you have the Omnibus package (which defaults to the recommendation above) please see [the Unicorn settings in the Omnibus GitLab documentation](https://docs.gitlab.com/omnibus/settings/unicorn.html).
## Redis and Sidekiq