<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>inference on Ritesh Sonawane</title><link>https://riteshsonawane.com/tags/inference/</link><description>Recent content in inference on Ritesh Sonawane</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 06 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://riteshsonawane.com/tags/inference/index.xml" rel="self" type="application/rss+xml"/><item><title>LLM Inference KPIs Every SRE Should Know</title><link>https://riteshsonawane.com/blog/llms-inference-kpis/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/llms-inference-kpis/</guid><description>&lt;p&gt;Monitoring LLM inference is not like monitoring a conventional web service. The metrics are different, the failure modes are different, and the relationship between what you measure and what the user experiences is more indirect.&lt;/p&gt;
&lt;p&gt;This guide explains the most useful LLM inference KPIs for SREs, what each metric measures, what causes it to change, and how to use the signals together when production performance degrades.&lt;/p&gt;
&lt;h2 id="the-mental-model-prefill-and-decode"&gt;The mental model: prefill and decode&lt;/h2&gt;
&lt;p&gt;Every LLM inference request goes through two distinct phases. If you do not understand the difference, the metrics will not make sense.&lt;/p&gt;</description></item><item><title>Kubernetes Gateway API Inference Extension</title><link>https://riteshsonawane.com/blog/k8s-gateway-api-inference/</link><pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/k8s-gateway-api-inference/</guid><description>&lt;h2 id="kubernetes-gateway-api-inference-extension-what-it-is-and-why-it-matters"&gt;Kubernetes Gateway API Inference Extension: What It Is and Why It Matters&lt;/h2&gt;
&lt;p&gt;If you are running LLM workloads on Kubernetes today, you have almost certainly hit the same wall. Your standard Ingress or Gateway routes traffic to pods based on HTTP path or headers. Round-robin distributes load across replicas. Everything looks fine from the control plane perspective. But your GPU utilization is uneven, some replicas are getting hammered while others sit idle, latency is unpredictable, and you have no way to differentiate a low-latency interactive chat request from a background batch job that can afford to wait.&lt;/p&gt;</description></item></channel></rss>