diff options
| author | Sean Carroll <scarroll@gitlab.com> | 2022-01-18 16:05:24 +0100 |
|---|---|---|
| committer | Sean Carroll <scarroll@gitlab.com> | 2022-01-18 16:05:24 +0100 |
| commit | f8d0559503672adf3a0fde55a9abe476306f107b (patch) | |
| tree | 24e8d3a3b476befb5009e73449a822b531b003d6 | |
| parent | 09516a824380e01191082ca38931efe0b8775e45 (diff) | |
| download | gitlab-shell-rate-limiting-docs.tar.gz | |
Update rate limit to 600/minuterate-limiting-docs
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -117,7 +117,7 @@ guidelines: GitLab Shell performs rate limiting by user account and project for git operations. GitLab Shell accepts git operation requests and then make a call to the Rails rate limiter (backed by Redis). If the `user + project` limit is exceeds the rate limit then GitLab shell will then drop further connection requests for that `user + project`. -The rate limiter is applied at the git command (plumbing) level. Each command has a rate limit of 60/minute - ie: `git push` has 60/minute and `git pull` has another 60/minute. +The rate limiter is applied at the git command (plumbing) level. Each command has a rate limit of 600/minute - ie: `git push` has 600/minute and `git pull` has another 600/minute. Because they are using the same plumbing command `git-upload-pack`, `git pull` and `git clone are in effect the same command for the purposes of rate limiting. |