summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJob van der Voort <jobvandervoort@gmail.com>2014-12-08 13:51:27 +0100
committerJob van der Voort <jobvandervoort@gmail.com>2014-12-08 13:51:27 +0100
commitb7d4184f24000fcdee7ca48fd802e35ac03abb67 (patch)
tree8d2fda84ba2f1b97e9c7eef8cc8618994a1eb1cd
parentbbf9953b99d59801c72dd7b9550ee149ca77bfcf (diff)
downloadgitlab-ce-b7d4184f24000fcdee7ca48fd802e35ac03abb67.tar.gz
advise about unicorn workers
-rw-r--r--config/unicorn.rb.example16
-rw-r--r--doc/install/requirements.md10
2 files changed, 18 insertions, 8 deletions
diff --git a/config/unicorn.rb.example b/config/unicorn.rb.example
index ea22744fd90..f8f441b1d42 100644
--- a/config/unicorn.rb.example
+++ b/config/unicorn.rb.example
@@ -13,9 +13,11 @@
#
# ENV['RAILS_RELATIVE_URL_ROOT'] = "/gitlab"
-# Use at least one worker per core if you're on a dedicated server,
-# more will usually help for _short_ waits on databases/caches.
-# The minimum is 2
+# We recommend using CPU cores + 1 worker processes.
+# Read more about unicorn workers here:
+# http://doc.gitlab.com/ee/install/requirements.html
+#
+# The minimum amount of worker processes is 2
worker_processes 2
# 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
# nuke workers after 30 seconds instead of 60 seconds (the default)
#
-# 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
-# you will have to increase this value too.
-#
+# 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
+# you will have to increase this value too.
+#
# Example of output if you try to push 1GB repo to GitLab over http.
# -> git push http://gitlab.... master
#
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index 660c1adb802..af7ac6146ad 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -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.
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
- 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)
- Opera (Latest released version)
- IE 10+