Namespace-level rate limits for GitLab.com
Problem
As usage of GitLab.com expands, we will see a wider array of customers (small to large enterprise) as well as use cases. This can present a challenge with some of our rate limits, as they cannot be configured at a namespace-level. This can present an impediment to adoption of GitLab.com, as there is no workaround for customers whose usage (whether due to raw size or usage patterns) may end up hitting one of the rate limits.
Proposed Solution
TBD. Namespace-level rate limits would be ideal so we can tune them as needed. This may be difficult however, as the rate limiting service would need to be namespace-aware.
Exploration
We need to gather some baseline data on what rate limits are likely to be problematic, and whether they can be changed.