advise about unicorn workers

This commit is contained in:
Job van der Voort 2014-12-08 13:51:27 +01:00
parent bbf9953b99
commit b7d4184f24
2 changed files with 18 additions and 8 deletions

View File

@ -13,9 +13,11 @@
# #
# ENV['RAILS_RELATIVE_URL_ROOT'] = "/gitlab" # ENV['RAILS_RELATIVE_URL_ROOT'] = "/gitlab"
# Use at least one worker per core if you're on a dedicated server, # We recommend using CPU cores + 1 worker processes.
# more will usually help for _short_ waits on databases/caches. # Read more about unicorn workers here:
# The minimum is 2 # http://doc.gitlab.com/ee/install/requirements.html
#
# The minimum amount of worker processes is 2
worker_processes 2 worker_processes 2
# Since Unicorn is never exposed to outside clients, it does not need to # Since Unicorn is never exposed to outside clients, it does not need to

View File

@ -88,6 +88,14 @@ Sidekiq processes the background jobs with a multithreaded process.
This process starts with the entire Rails stack (200MB+) but it can grow over time due to memory leaks. This process starts with the entire Rails stack (200MB+) but it can grow over time due to memory leaks.
On a very active server (10,000 active users) the Sidekiq process can use 1GB+ of memory. On a very active server (10,000 active users) the Sidekiq process can use 1GB+ of memory.
## Unicorn Workers
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 a machine with 2 cores, 3 unicorn workers is ideal.
## Supported web browsers ## Supported web browsers
- Chrome (Latest stable version) - Chrome (Latest stable version)