GitLab 率限变更影响 LLM 使用
问题概述
GitLab.com 正在调整未授权和免费计划的请求配额，导致每分钟仅限一条请求的限制。这对依赖大量 API 调用的 LLM 交互和数据抓取场景造成显著瓶颈，用户担忧率限不足并呼吁更高配额或替代方案。
痛点标签
- 未授权请求每小时仅限 60 条（即每分钟一条）
- 免费计划每小时 5,000 条请求仍可能不足以满足高频 LLM 使用
- 率限限制导致 LLM 与 GitLab 的交互变得低效
待验证问题
- 用户主要受益于当前的免费配额吗？
- 是否需要更高的未授权请求配额来支持 LLM 使用？
- 是否有其他替代方案（如自托管或 GraphQL）被用户考虑？
证据
原话 · @匿名
If you are using LLMs to interact with sites like GitLab and GitHub, and you have the option to use a GraphQL API, you should jump on it immediately. GraphQL is absolutely terrible for human developers to interact with, but it's like Facebook could see into the future back in 2012. I cannot imagine a more perfect API surface for agents. With the REST API on GitHub, you can consume maybe 10 issue JSON blobs before your context window is blown out. With GraphQL constraining the results you can easily read hundreds in the same token budget. Additionally, the # of requests your agents need to make can be reduced in many cases since GraphQL can join across types whereas REST APIs cannot. You essentially get savings in two dimensions here. Quota and raw token volume per logical response.
原话 · @匿名
60/hour unauthenticated, but 5,000/hour on the free plan.60/hour sucks. 5000/hour (a little more than one per second) is totally fine.I'm chalking this up alongside Docker's decision to restrict unauthenticated pulls. Unauthenticated anything went the way of the dodo some time ago. If you want unauthenticated access, go run your own mirror.
原话 · @匿名
I assume this is because of LLM scraping.
免责声明：本卡片由 AI 从社区讨论中提炼，属于「痛点证据」，是需求分析与验证的起点，不等同于「已验证的市场需求」。AI 存在分析局限，关键决策前请打开上方原始讨论人工复核。