diff options
| author | Sytse Sijbrandij <sytse@gitlab.com> | 2016-12-28 14:37:58 +0300 |
|---|---|---|
| committer | Sytse Sijbrandij <sytse@gitlab.com> | 2016-12-28 14:37:58 +0300 |
| commit | 6c238a8c00413f3c5ea178f45145698f739497f7 (patch) | |
| tree | 9ef05c0f7b8f7f0df78db00115730972a20dc288 | |
| parent | 850ee2eb96937429ca1c91c22093cf1b3e0e9f0a (diff) | |
| parent | b3a9a7af9164a03bb3d7c4b27228af603ea4e59a (diff) | |
Merge branch 'master' of gitlab.com:gitlab-org/gitaly
| -rw-r--r-- | README.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -24,6 +24,8 @@ To see where it fits in please look at [GitLab's architecture](https://docs.gitl - [Lots of thinking in issue 2](https://gitlab.com/gitlab-org/gitaly/issues/2) - [Git Pack Protocol Reference](https://github.com/git/git/blob/master/Documentation/technical/pack-protocol.txt) - [Git Transfer Protocol internals](https://git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols) +- [E3 Elastic Experiment Executor](https://bitbucket.org/atlassian/elastic-experiment-executor) + ## Name @@ -72,6 +74,8 @@ All design decision should be added here. 1. How will the networking work? A unix socket for git operations and TCP for monitoring. This prevents having to build out authentication at this early stage. https://gitlab.com/gitlab-org/gitaly/issues/16 1. We'll include the /vendor directory in source control https://gitlab.com/gitlab-org/gitaly/issues/18 1. Use gitaly-client or HTTP/websocket clients? gitlab-shell copies the SSH stream, both ways, to gitaly over a websocket, workhorse just forwards the request to Gitaly, let’s use HTTP. https://gitlab.com/gitlab-org/gitaly/issues/5#note_20294280 +1. We will use [E3 from BitBucket to measure performance closely in isolation](https://gitlab.com/gitlab-org/gitaly/issues/34). + ## Iterate |