diff options
author | DJ Mountney <david@twkie.net> | 2016-05-05 23:46:58 +0300 |
---|---|---|
committer | DJ Mountney <david@twkie.net> | 2016-05-05 23:46:58 +0300 |
commit | d6f67dba0144bdae20bd86051f3eb98ce201439e (patch) | |
tree | c364eec90d53ce3f3d2a64991f03c50638e345b4 /doc/install | |
parent | 56c49f4fb50b3b1fe170c93d8a0f67ec4e32888f (diff) |
Add note to requirements doc on swap recommendation, and ensuring enough available memory.
Diffstat (limited to 'doc/install')
-rw-r--r-- | doc/install/requirements.md | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md index 58f409746cd..df8e8bdc476 100644 --- a/doc/install/requirements.md +++ b/doc/install/requirements.md @@ -64,7 +64,10 @@ If you have enough RAM memory and a recent CPU the speed of GitLab is mainly lim ### Memory You need at least 2GB of addressable memory (RAM + swap) to install and use GitLab! -With less memory GitLab will give strange errors during the reconfigure run and 500 errors during usage. +The operating system and any other running applications will also be using memory +so keep in mind that you need at least 2GB available before running GitLab. With +less memory GitLab will give strange errors during the reconfigure run and 500 +errors during usage. - 512MB RAM + 1.5GB of swap is the absolute minimum but we strongly **advise against** this amount of memory. See the unicorn worker section below for more advice. - 1GB RAM + 1GB swap supports up to 100 users but it will be very slow @@ -77,6 +80,10 @@ With less memory GitLab will give strange errors during the reconfigure run and - 128GB RAM supports up to 32,000 users - More users? Run it on [multiple application servers](https://about.gitlab.com/high-availability/) +We recommend having at least 1GB of swap on your server, even if you currently have +enough available RAM. Having swap will help reduce the chance of errors occuring +if your available memory changes. + Notice: The 25 workers of Sidekiq will show up as separate processes in your process overview (such as top or htop) but they share the same RAM allocation since Sidekiq is a multithreaded application. Please see the section below about Unicorn workers for information about many you need of those. ## Gitlab Runner |