diff options
| author | Darwin Sanoy <dsanoy@gitlab.com> | 2021-04-22 16:26:24 +0300 |
|---|---|---|
| committer | Darwin Sanoy <dsanoy@gitlab.com> | 2021-04-22 16:26:24 +0300 |
| commit | 894da6006bbf34710bf1221f083b37eabeba4f6a (patch) | |
| tree | e7261629dd2d7d131ad6435aacaa499b6ff62244 /doc | |
| parent | 95d36a9400438c55fa6dc980f5caf8b5b099567d (diff) | |
update
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/DESIGN.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/DESIGN.md b/doc/DESIGN.md index 8913a3a8a..7312bddd2 100644 --- a/doc/DESIGN.md +++ b/doc/DESIGN.md @@ -23,7 +23,7 @@ Gitaly is a layer that brings horizontal scaling and higher availability to mass These workload characteristics are not fundamentally predictable across the portfolio of source code that a given GitLab server may need to store. Large monorepos might exist at companies with few employees. Binaries storage - while not considered an ideal file type for Git file systems - is common in some industry segments or project types. This means that architecting a GitLab instance with built-in Git headroom limitations causes unexpected limitations of specific Git usage patterns of the people using the instance. -These are some of the most challenging git workloads for (like some database ops would). Containers are very memory constrained and brutal measures are taken when containers attempt to exceed limits. +These are some of the most challenging git workloads for Git: - Large scale monorepos (commits and packs for full clones are very large). - High commit volume on a single repository (commits and packs for full clones are very frequent). - Binaries stored in the Git file system. (In GitLab Git LFS can be redirected to PaaS storage). |