<?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>Rpm on Wilson Wu</title><link>https://wilsonwu.me/en/tags/rpm/</link><description>Recent content in Rpm on Wilson Wu</description><generator>Hugo -- 0.127.0</generator><language>en-US</language><lastBuildDate>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wilsonwu.me/en/tags/rpm/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Distributed AI Rate Limiting Server with RPM and TPM Support Using Envoy Ratelimit</title><link>https://wilsonwu.me/en/blog/2026/envoy-ai-ratelimit/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://wilsonwu.me/en/blog/2026/envoy-ai-ratelimit/</guid><description>For conventional HTTP APIs, limiting the number of requests per minute is usually enough. For large language model APIs, however, limiting only the request count is far from sufficient: one request may consume only a few dozen tokens, while another may consume tens of thousands.
Therefore, a practical AI gateway usually needs to support all of the following:
RPM (Requests Per Minute): the number of requests per minute. TPM (Tokens Per Minute): the number of tokens per minute.</description></item></channel></rss>