diff options
| author | Darwin Sanoy <dsanoy@gitlab.com> | 2021-04-26 18:27:55 +0300 |
|---|---|---|
| committer | Darwin Sanoy <dsanoy@gitlab.com> | 2021-04-26 18:27:55 +0300 |
| commit | 17b5072fb3b4cf9ce5125824348c2d0cab63d9fc (patch) | |
| tree | 20c87499c76ff235aa0fc0cb16fedb43556a785c /doc/DESIGN.md | |
| parent | 9566f93d2c1c4973facb1132a2ce6b0459f8195e (diff) | |
Add word busy
Diffstat (limited to 'doc/DESIGN.md')
| -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 923b84adc..43e8c7572 100644 --- a/doc/DESIGN.md +++ b/doc/DESIGN.md @@ -24,7 +24,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 Git: -- Large scale monorepos (commit volume is and packs for full clones are very large). +- Large scale, busy monorepos (commit volume is 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 object database. (In GitLab Git LFS can be redirected to PaaS storage). - Full history cloning - due to packfile creation requirements. |