Memory requirements are dependent on the number of users and expected workload. More users? Consult the reference architectures page Memory.4 cores is the recommended minimum number of cores and supports up to 500 users.The following is the recommended minimum CPU hardware guidance for a handful of example GitLab user base sizes.
Your workload is influenced by factors such as - but not limited to - how active your users are, how much automation you use, mirroring, and repository/change size. Your exact needs may be more, depending on your workload.
CPUĬPU requirements are dependent on the number of users and expected workload. See our official Statement of Support for further information. NFS for Git repository storage is deprecated. Having a fast drive (7200 RPM and up) or a solid state drive (SSD) improves the responsiveness of GitLab. If you have enough RAM and a recent CPU the speed of GitLab is mainly limited by hard drive seek times. 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 want to be flexible about growing your hard drive space in the future consider mounting it using logical volume management (LVM) so you can add more hard drives when you need them.Īpart from a local hard drive you can also mount a volume that supports the network file system (NFS) protocol. The Omnibus GitLab package requires about 2.5 GB of storage space for installation. The necessary hard drive space largely depends on the size of the repositories you want to store in GitLab but as a guideline you should have at least as much free space as all your repositories combined take up. Omnibus GitLab packages starting with GitLab 13.9. Redis version 6.0 or higher is recommended, as this is what ships with GitLab 13.0 and later requires Redis version 5.0 or higher. This page includes information about the minimum requirements you need to install and use GitLab.
0 kommentar(er)
