<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Rate Limit on Mengboy 技术笔记</title>
    <link>https://www.mfun.ink/tags/rate-limit/</link>
    <description>Recent content in Rate Limit on Mengboy 技术笔记</description>
    <generator>Hugo -- 0.156.0</generator>
    <language>zh-cn</language>
    <lastBuildDate>Fri, 03 Apr 2026 01:15:05 +0000</lastBuildDate>
    <atom:link href="https://www.mfun.ink/tags/rate-limit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Claude API Rate-Limit Storm Playbook: Adaptive Concurrency, Jittered Backoff, and Quota Isolation</title>
      <link>https://www.mfun.ink/english/post/claude-api-rate-limit-storm-adaptive-concurrency-backoff-quota-isolation/</link>
      <pubDate>Fri, 03 Apr 2026 01:15:05 +0000</pubDate>
      <guid>https://www.mfun.ink/english/post/claude-api-rate-limit-storm-adaptive-concurrency-backoff-quota-isolation/</guid>
      <description>&lt;p&gt;When Claude API starts returning 429 under high load, most systems don&amp;rsquo;t just slow down—they collapse: queue buildup, retry storms, upstream timeout chains, and pager noise.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Claude API 高并发限流雪崩应对：自适应并发、退避抖动与配额隔离</title>
      <link>https://www.mfun.ink/2026/04/03/claude-api-rate-limit-storm-adaptive-concurrency-backoff-quota-isolation/</link>
      <pubDate>Fri, 03 Apr 2026 01:15:05 +0000</pubDate>
      <guid>https://www.mfun.ink/2026/04/03/claude-api-rate-limit-storm-adaptive-concurrency-backoff-quota-isolation/</guid>
      <description>&lt;p&gt;当 Claude API 在高并发下开始返回 429，很多系统不是“慢一点”，而是直接雪崩：队列堆积、重试风暴、上游超时、下游告警连锁。&lt;/p&gt;</description>
    </item>
    <item>
      <title>OpenAI Responses 在 Go 多租户中的配额治理：令牌桶限流、预算熔断与账单归因</title>
      <link>https://www.mfun.ink/2026/03/20/openai-responses-go-multitenant-quota-governance/</link>
      <pubDate>Fri, 20 Mar 2026 01:08:00 +0000</pubDate>
      <guid>https://www.mfun.ink/2026/03/20/openai-responses-go-multitenant-quota-governance/</guid>
      <description>&lt;p&gt;多租户 AI 服务最容易死在两件事：&lt;strong&gt;一个租户打爆全局配额&lt;/strong&gt;，以及&lt;strong&gt;月底账单炸了才发现&lt;/strong&gt;。&lt;/p&gt;
&lt;p&gt;这篇给你一套可直接落地的 Go 方案：令牌桶限流 + 预算熔断 + 账单归因，目标是“先活下来，再精细化”。&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
