Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitaly.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorDarwin Sanoy <dsanoy@gitlab.com>2021-04-22 16:27:36 +0300
committerDarwin Sanoy <dsanoy@gitlab.com>2021-04-22 16:27:36 +0300
commit6379051b6bb819dedaaa575a7cdcd4679176ff94 (patch)
tree7227a67590d731ea8be832858099d46f375fa6ee /doc
parent894da6006bbf34710bf1221f083b37eabeba4f6a (diff)
updates
Diffstat (limited to 'doc')
-rw-r--r--doc/DESIGN.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/DESIGN.md b/doc/DESIGN.md
index 7312bddd2..a20eec6fb 100644
--- a/doc/DESIGN.md
+++ b/doc/DESIGN.md
@@ -32,7 +32,7 @@ These are some of the most challenging git workloads for Git:
The above workload factors compound together when a given workload has more than one characteristic.
#### Affects on Horizontal Compute Architecture
- The memory burstiness profile of Git makes it (and therefore Gitaly) very challenging to reliably containerize because container systems have very strong memory limits. Exceeding these limits causes significant operational instability and/or termination by the container running system.
-- The disk IO burstiness profile of Git makes it (and therefore Gitaly) very challenging to use remote file systems with reliability and integrity (e.g. NFS - including PaaS versions). This was, in fact, the first design reason for Gitaly - to keep "Git" from having to operate on remote storage.
+- The disk IO burstiness profile of Git makes it (and therefore Gitaly) very challenging to use remote file systems with reliability and integrity (e.g. NFS - including PaaS versions). This was, in fact, the first design reason for Gitaly - to avoid having the Git binary operate on remote storage.
- The CPU burstiness profile of Git (and therefore Gitaly) also makes it challenging to reliably containerize.
These are the challenges that imply an application layer is needed to help Git scale horizontally in any scaled implementation - not just GitLab. GitLab has built this layer and continues to chip away (iterate) against all of the above challenges in this innovative layer.