Download as
Browse Code »

Commit 363c5204d9947444eb955aa59861c8c5a2f6faf5

Authored by Sytse Sijbrandij
1 parent 1a6ba7e6
Exists in master and in 4 other branches 6-8-stable, 7-0-stable, 7-0-stable-spb, spb-stable

Better requirements based on the experience of GitLab Cloud.

Showing 1 changed file with 13 additions and 6 deletions   Show diff stats
doc/install/requirements.md
  Diff comments   View file @363c520
... ... @@ -41,23 +41,30 @@ some work on your part.
41 41  
42 42 ## CPU
43 43  
44   -We recommend a processor with **4 cores**. At a minimum you need a processor with 2 cores to responsively run an unmodified installation.
  44 +- 1 core works for under 100 users but the responsiveness might suffer
  45 +- **2 cores** is the **recommended** number of cores and supports up to 100 users
  46 +- 4 cores supports about 1,000 users
  47 +- 8 cores supports up to 10,000 users
45 48  
46 49 ## Memory
47 50  
48 51 - 512MB is too little memory, GitLab will be very slow and you will need 250MB of swap
49   -- 768MB is the minimal memory size and supports up to 100 users
50   -- **1GB** is the **recommended** memory size and supports up to 1,000 users
51   -- 1.5GB supports up to 10,000 users
  52 +- 768MB is the minimal memory size but we advise against this
  53 +- 1GB supports up to 100 users if you do not have individual repo's over 250MB
  54 +- **2GB** is the **recommended** memory size and supports up to 1,000 users
  55 +- 4GB supports up to 10,000 users
52 56  
53 57 ## Storage
54 58  
55 59 The necessary hard drive space largely depends on the size of the repos you want
56 60 to store in GitLab. But as a *rule of thumb* you should have at least twice as much
57   -free space as your all repos combined take up. You need twice the storage because [GitLab satellites](structure.md) contain an extra copy of each repo. Apart from a local hard drive you can also mount a volume that supports the network file system (NFS) protocol. This volume might be located on a file server, a network attached storage (NAS) device, a storage area network (SAN) or on an Amazon Web Services (AWS) Elastic Block Store (EBS) volume.
  61 +free space as your all repos combined take up. You need twice the storage because [GitLab satellites](structure.md) contain an extra copy of each repo.
58 62  
59   -If you have enough RAM memory and a recent CPU the speed of GitLab is mainly limited by hard drive seek times. Having a fast drive (7200 RPM and up) or a solid state drive (SSD) will improve the responsiveness of GitLab.
  63 +If you want to be flexible about growing your hard drive space in the future consider mounting it using LVM so you can add more hard drives when you need them.
  64 +
  65 +Apart from a local hard drive you can also mount a volume that supports the network file system (NFS) protocol. This volume might be located on a file server, a network attached storage (NAS) device, a storage area network (SAN) or on an Amazon Web Services (AWS) Elastic Block Store (EBS) volume.
60 66  
  67 +If you have enough RAM memory and a recent CPU the speed of GitLab is mainly limited by hard drive seek times. Having a fast drive (7200 RPM and up) or a solid state drive (SSD) will improve the responsiveness of GitLab.
61 68  
62 69 # Installation troubles and reporting success or failure
63 70  
... ...