Application and rate limit guidelines
GitLab, like most large applications, enforces limits in certain features. The absences of limits can affect security, performance, data, or could even exhaust the allocated resources for the application.
Every new feature should have safe usage limits included in its implementation. Limits are applicable for:
- System-level resource pools such as API requests, SSHD connections, database connections, and storage.
- Domain-level objects such as compute quota, groups, and sign-in attempts.
When limits are required
- Limits are required if the absence of the limit matches severity 1 - 3 in the severity definitions for limit-related bugs.
- GitLab application limits documentation must be updated anytime limits are added, removed, or updated.
Additional reading
- Existing GitLab application limits
- Product processes: introducing application limits
- Development documentation: guide for adding application limits
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support