We recommend a processor with **4 cores**. At a minimum you need a processor with 2 cores to responsively run an unmodified installation.
- 1 core works for under 100 users but the responsiveness might suffer
-**2 cores** is the **recommended** number of cores and supports up to 100 users
- 4 cores supports about 1,000 users
- 8 cores supports up to 10,000 users
## Memory
## Memory
- 512MB is too little memory, GitLab will be very slow and you will need 250MB of swap
- 512MB is too little memory, GitLab will be very slow and you will need 250MB of swap
- 768MB is the minimal memory size and supports up to 100 users
- 768MB is the minimal memory size but we advise against this
-**1GB** is the **recommended** memory size and supports up to 1,000 users
- 1GB supports up to 100 users if you do not have individual repo's over 250MB
- 1.5GB supports up to 10,000 users
-**2GB** is the **recommended** memory size and supports up to 1,000 users
- 4GB supports up to 10,000 users
## Storage
## Storage
The necessary hard drive space largely depends on the size of the repos you want
The necessary hard drive space largely depends on the size of the repos you want
to store in GitLab. But as a *rule of thumb* you should have at least twice as much
to store in GitLab. But as a *rule of thumb* you should have at least twice as much
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.
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.
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.
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.
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.
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.
# Installation troubles and reporting success or failure
# Installation troubles and reporting success or failure
