Merge branch 'unicorn-workers' into 'master'

Documentation about unicorn settings.

Helps with https://news.ycombinator.com/item?id=9213180

See merge request !1704

1 files changed, 4 insertions, 1 deletions

diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index 65ddb3e3cfb..f42af65796f 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -76,7 +76,8 @@ Notice: The 25 workers of Sidekiq will show up as separate processes in your pro
 
 ## Unicorn Workers
 
-It's possible to increase the amount of unicorn workers and tis will usually help for to reduce the response time of the applications.
+It's possible to increase the amount of unicorn workers and tis will usually help for 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.
 
@@ -85,6 +86,8 @@ If you have a 512MB machine with a magnetic (non-SSD) swap drive we recommend to
 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 512MB machine with a SSD drive you can use two Unicorn workers, this will allow HTTP access although it will be slow due to 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).
+
 ## Database
 
 If you want to run the database separately, the **recommended** database size is **1 MB per user**.