summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Johnson <ejohnson@gitlab.com>2019-03-05 04:22:33 +0000
committerEric Johnson <ejohnson@gitlab.com>2019-03-05 04:22:33 +0000
commitf786dcb255ae3e2eb3618b09a474b90a34d6f743 (patch)
treed7487a3b5585f4e19464bec9f5b3da6f7ee6f232
parent7b4130d0f7390629d683e4365279ab5554bbcfc4 (diff)
downloadgitlab-ce-f786dcb255ae3e2eb3618b09a474b90a34d6f743.tar.gz
Adding NFS warning to requirements
-rw-r--r--doc/install/requirements.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index c1f2297f3be..8ab7189c2a6 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -51,6 +51,8 @@ Apart from a local hard drive you can also mount a volume that supports the netw
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.
+NOTE: **Note:** Since file system performance may affect GitLab's overall performance, we do not recommend using EFS for storage. See the [relevant documentation](../administration/high_availability/nfs.md#avoid-using-awss-elastic-file-system-efs) for more details.
+
### CPU
- 1 core supports up to 100 users but the application can be a bit slower due to having all workers and background jobs running on the same core