Commit b7d4184f authored by Job van der Voort's avatar Job van der Voort

advise about unicorn workers

parent bbf9953b
...@@ -13,9 +13,11 @@ ...@@ -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
...@@ -37,10 +39,10 @@ listen "127.0.0.1:8080", :tcp_nopush => true ...@@ -37,10 +39,10 @@ listen "127.0.0.1:8080", :tcp_nopush => true
# nuke workers after 30 seconds instead of 60 seconds (the default) # nuke workers after 30 seconds instead of 60 seconds (the default)
# #
# NOTICE: git push over http depends on this value. # NOTICE: git push over http depends on this value.
# If you want be able to push huge amount of data to git repository over http # If you want be able to push huge amount of data to git repository over http
# you will have to increase this value too. # you will have to increase this value too.
# #
# Example of output if you try to push 1GB repo to GitLab over http. # Example of output if you try to push 1GB repo to GitLab over http.
# -> git push http://gitlab.... master # -> git push http://gitlab.... master
# #
......
...@@ -88,10 +88,18 @@ Sidekiq processes the background jobs with a multithreaded process. ...@@ -88,10 +88,18 @@ 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)
- Firefox (Latest released version and [latest ESR version](https://www.mozilla.org/en-US/firefox/organizations/)) - Firefox (Latest released version and [latest ESR version](https://www.mozilla.org/en-US/firefox/organizations/))
- Safari 7+ (known problem: required fields in html5 do not work) - Safari 7+ (known problem: required fields in html5 do not work)
- Opera (Latest released version) - Opera (Latest released version)
- IE 10+ - IE 10+
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