ContextQMD
Back to Gitlabhq

Rate limits on Git LFS

doc/administration/settings/git_lfs_rate_limits.md

18.11.22.0 KB
Original Source

{{< details >}}

  • Tier: Free, Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

Git Large File Storage (LFS) is a Git extension for handling large files. If you use Git LFS in your repository, common Git operations can generate many Git LFS requests. You can enforce general user and IP rate limits, but you can also override the general setting to enforce additional limits on Git LFS requests. This override can improve the security and durability of your web application.

On GitLab.com

On GitLab.com, Git LFS requests are subject to authenticated web request rate limits. These limits are set to 1000 requests per minute per user.

Each Git LFS object uploaded or downloaded generates an HTTP request that counts toward this limit.

[!note] Projects with multiple large files may encounter an HTTP rate limit error. This error occurs during cloning or pulling, when performed from a single IP address in automated environments like CI/CD pipelines.

On GitLab Self-Managed

Git LFS rate limits are disabled by default on GitLab Self-Managed instances. Administrators can configure dedicated rate limits specifically for Git LFS traffic. When enabled, these dedicated LFS rate limits override the default user and IP rate limits.

Configure Git LFS rate limits

Prerequisites:

  • You must be an administrator for the instance.

To configure Git LFS rate limits:

  1. In the upper-right corner, select Admin.
  2. Select Settings > Network.
  3. Expand Git LFS Rate Limits.
  4. Select Enable authenticated Git LFS request rate limit.
  5. Enter a value for Max authenticated Git LFS requests per period per user.
  6. Enter a value for Authenticated Git LFS rate limit period in seconds.
  7. Select Save changes.