<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Batching on Rik Kisnah - Blog</title><link>https://www.rik-kisnah.ai/tags/batching/</link><description>Recent content in Batching on Rik Kisnah - Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 11 Nov 2025 09:00:00 -0800</lastBuildDate><atom:link href="https://www.rik-kisnah.ai/tags/batching/feed.xml" rel="self" type="application/rss+xml"/><item><title>Design an Inference API</title><link>https://www.rik-kisnah.ai/teach/gpu-ai/design-an-inference-api/</link><pubDate>Tue, 11 Nov 2025 09:00:00 -0800</pubDate><guid>https://www.rik-kisnah.ai/teach/gpu-ai/design-an-inference-api/</guid><description>Thousands of people send prompts, a pool of GPUs answers them, and the GPU only earns its keep when it works on many prompts at once. Design the layer in between: the batcher, the queues, the maths for how many GPUs, what happens when one dies, and how two models share eight GPUs when one of them needs all eight.</description></item><item><title>Continuous Batching for Inference</title><link>https://www.rik-kisnah.ai/teach/gpu-ai/continuous-batching-for-inference/</link><pubDate>Tue, 15 Apr 2025 09:00:00 -0700</pubDate><guid>https://www.rik-kisnah.ai/teach/gpu-ai/continuous-batching-for-inference/</guid><description>Generating text is one token at a time, and one token uses a fraction of the GPU. So you serve many conversations at once and swap them in and out as they finish, every single step. This is why a serving engine is not just &amp;lsquo;call the model in a loop&amp;rsquo;.</description></item></channel></rss>