diff options
| -rw-r--r-- | config/unicorn.rb.example | 6 | ||||
| -rw-r--r-- | doc/install/requirements.md | 4 |
2 files changed, 5 insertions, 5 deletions
diff --git a/config/unicorn.rb.example b/config/unicorn.rb.example index f8f441b1d42..d8b4f5c7c32 100644 --- a/config/unicorn.rb.example +++ b/config/unicorn.rb.example @@ -13,11 +13,9 @@ # # ENV['RAILS_RELATIVE_URL_ROOT'] = "/gitlab" -# We recommend using CPU cores + 1 worker processes. -# Read more about unicorn workers here: -# http://doc.gitlab.com/ee/install/requirements.html +# Read about unicorn workers here: +# http://doc.gitlab.com/ee/install/requirements.html#unicorn-workers # -# The minimum amount of worker processes is 2 worker_processes 2 # Since Unicorn is never exposed to outside clients, it does not need to diff --git a/doc/install/requirements.md b/doc/install/requirements.md index af7ac6146ad..28e1fa34d23 100644 --- a/doc/install/requirements.md +++ b/doc/install/requirements.md @@ -93,9 +93,11 @@ On a very active server (10,000 active users) the Sidekiq process can use 1GB+ o It's possible to increase the amount of unicorn workers. This will usually help for short waits on databases and caches. -We recommend using CPU cores + 1 unicorn workers. +For most instances we recommend using CPU cores + 1 unicorn workers. For a machine with 2 cores, 3 unicorn workers is ideal. +For memory constrained instances, we recommend using a single unicorn worker. + ## Supported web browsers - Chrome (Latest stable version) |