diff options
| author | Sytse Sijbrandij <sytses@gmail.com> | 2014-06-24 10:29:50 +0200 |
|---|---|---|
| committer | Sytse Sijbrandij <sytses@gmail.com> | 2014-06-24 10:29:50 +0200 |
| commit | f4398835f4e9ce380c52142b7a407b3ec922905f (patch) | |
| tree | bc23de85a542c56b4d3fdf85e6539ea8b6132ff5 | |
| parent | 614e0857d66f5635eead6270e70d6c7d337a1ff1 (diff) | |
| download | gitlab-ce-f4398835f4e9ce380c52142b7a407b3ec922905f.tar.gz | |
Some background on Redis and Sidekiq requirements.
| -rw-r--r-- | doc/install/requirements.md | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md index 9f7c03badcf..ccfa670565e 100644 --- a/doc/install/requirements.md +++ b/doc/install/requirements.md @@ -84,7 +84,15 @@ If you have enough RAM memory and a recent CPU the speed of GitLab is mainly lim ## Database -If you want to run the database separately, the **recommended** database size is **1 MB per user** +If you want to run the database separately, the **recommended** database size is **1 MB per user**. + +## Redis and Sidekiq + +Redis stores all user sessions and the background task queue. +The storage requirements for Redis are minimal, about 1kB per user. +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. ## Supported webbrowsers |