Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
gitlab-ce
Commits
f811b695
Commit
f811b695
authored
Dec 08, 2014
by
Job van der Voort
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
memory constrained unicorn workers
parent
b7d4184f
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
5 additions
and
5 deletions
+5
-5
config/unicorn.rb.example
config/unicorn.rb.example
+2
-4
doc/install/requirements.md
doc/install/requirements.md
+3
-1
No files found.
config/unicorn.rb.example
View file @
f811b695
...
@@ -13,11 +13,9 @@
...
@@ -13,11 +13,9 @@
#
#
# ENV['RAILS_RELATIVE_URL_ROOT'] = "/gitlab"
# ENV['RAILS_RELATIVE_URL_ROOT'] = "/gitlab"
# We recommend using CPU cores + 1 worker processes.
# Read about unicorn workers here:
# Read more about unicorn workers here:
# http://doc.gitlab.com/ee/install/requirements.html#unicorn-workers
# 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
...
...
doc/install/requirements.md
View file @
f811b695
...
@@ -93,9 +93,11 @@ On a very active server (10,000 active users) the Sidekiq process can use 1GB+ o
...
@@ -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.
It's possible to increase the amount of unicorn workers.
This will usually help for short waits on databases and caches.
This will usually help for short waits on databases and caches.
W
e recommend using CPU cores + 1 unicorn workers.
For most instances w
e recommend using CPU cores + 1 unicorn workers.
For a machine with 2 cores, 3 unicorn workers is ideal.
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
## Supported web browsers
-
Chrome (Latest stable version)
-
Chrome (Latest stable version)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment