diff options
| author | John Woods <jwoods@gitlab.com> | 2017-08-09 02:08:45 +0300 |
|---|---|---|
| committer | John Woods <jwoods@gitlab.com> | 2017-08-09 02:08:45 +0300 |
| commit | 22995bdb3fdd9c882a224823411ee61015c2f071 (patch) | |
| tree | 6f9a935c9023ee17032b22b65b8d204ed3bab39d /doc/administration/high_availability | |
| parent | 8d2099cd8ab02209a0c7aeccc43ecba57a07ae2a (diff) | |
Update nfs.md with information on AWS EFS and Burst Credit usage and how to increase Burst Credit limits and also limit the need for AWS to access EFS by using FS Cache.
Diffstat (limited to 'doc/administration/high_availability')
| -rw-r--r-- | doc/administration/high_availability/nfs.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/administration/high_availability/nfs.md b/doc/administration/high_availability/nfs.md index 90a2e9298bf..e09ccaba08c 100644 --- a/doc/administration/high_availability/nfs.md +++ b/doc/administration/high_availability/nfs.md @@ -42,6 +42,10 @@ GitLab does not recommend using EFS with GitLab. are allocated. For smaller volumes, users may experience decent performance for a period of time due to 'Burst Credits'. Over a period of weeks to months credits may run out and performance will bottom out. +- To keep "Burst Credits" available, it may be necessary to provision more space + with 'dummy data'. However, this may get expensive. +- Another option to maintain "Burst Credits" is to use FS Cache on the server so + that AWS doesn't always have to go into EFS to access files. - For larger volumes, allocated IOPS may not be the problem. Workloads where many small files are written in a serialized manner are not well-suited for EFS. EBS with an NFS server on top will perform much better. |