<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ai-Infrastructure on ROBOCO</title>
    <link>https://roboco.io/en/tags/ai-infrastructure/</link>
    <description>Recent content in Ai-Infrastructure on ROBOCO</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 28 Oct 2026 10:00:00 +0900</lastBuildDate>
    <atom:link href="https://roboco.io/en/tags/ai-infrastructure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Does LLM Caching Work? Reading AI Infrastructure Efficiency Through Anthropic’s S-1</title>
      <link>https://roboco.io/en/posts/how-llm-caching-works/</link>
      <pubDate>Wed, 28 Oct 2026 10:00:00 +0900</pubDate>
      <guid>https://roboco.io/en/posts/how-llm-caching-works/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;Anthropic’s S-1 describes reductions in the inference compute needed to deliver a given level of model performance, alongside improvements in how efficiently that compute is used in production. – Summary of “Compute Efficiency”&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://roboco.io/posts/images/Dohyun.png&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;h4&gt;Dohyun Jung - Principal Consultant, ROBOCO&lt;/h4&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;LLM infrastructure is evolving to require less compute for a task at a given performance level and to make better use of available resources. Anthropic’s discussion of inference efficiency in its S-1 is one piece of evidence for that trend.&lt;/li&gt;&#xA;&lt;li&gt;Prompt caching reuses the KV cache produced while processing an identical input prefix. It reduces repeated computation over long documents, while new questions still need processing and answers still need generating.&lt;/li&gt;&#xA;&lt;li&gt;At scale, systems share common computations in memory blocks and route requests with both cache location and load in mind. Some also store caches outside GPU memory.&lt;/li&gt;&#xA;&lt;li&gt;Improving cache efficiency starts with deciding whose computations may be shared with whom. User isolation can reduce reuse, and the same authorization boundaries must follow caches outside the GPU.&lt;/li&gt;&#xA;&lt;li&gt;The benefits depend on reuse frequency, available memory, and transfer costs. The reduction in reprocessed input tokens must not be treated as the reduction in total cost.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;Imagine visiting a support specialist with the same product manual. On the first day, the specialist has to read it from the beginning. You return the next day with a different question, but the specialist starts reading the entire manual again. Repeated reading could take longer than answering the question.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
