diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-26 06:07:43 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-26 06:07:43 +0300 |
| commit | dddde902acfa6acfb11583c61faa67cc7c8d11b6 (patch) | |
| tree | 2e9fdf963c84f82995d62d0c55f91168cff3ec47 /doc/development/merge_request_performance_guidelines.md | |
| parent | 101c30f4dffc624af3cbe3f12edc2cfee570a5f3 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/merge_request_performance_guidelines.md')
| -rw-r--r-- | doc/development/merge_request_performance_guidelines.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/merge_request_performance_guidelines.md b/doc/development/merge_request_performance_guidelines.md index 7f5ffe525af..d395bf13982 100644 --- a/doc/development/merge_request_performance_guidelines.md +++ b/doc/development/merge_request_performance_guidelines.md @@ -435,7 +435,7 @@ We can consider the following types of storages: ### Temporary storage The storage on production nodes is really sparse. The application should be built -in a way that accomodates running under very limited temporary storage. +in a way that accommodates running under very limited temporary storage. You can expect the system on which your code runs has a total of `1G-10G` of temporary storage. However, this storage is really shared across all jobs being run. If your job requires to use more than `100MB` of that space |