BigW Consortium Gitlab

Commit f811b695 by Job van der Voort

memory constrained unicorn workers

parent b7d4184f
......@@ -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
......
......@@ -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)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment