<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Planning your deployment on AI Tools</title>
    <link>https://ait.bsc.es/handbook/planning-your-deployment/</link>
    <description>Recent content in Planning your deployment on AI Tools</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://ait.bsc.es/handbook/planning-your-deployment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Choosing the right model</title>
      <link>https://ait.bsc.es/handbook/planning-your-deployment/choosing-the-right-model/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/handbook/planning-your-deployment/choosing-the-right-model/</guid>
      <description>&lt;p&gt;The largest model that fits is rarely the right choice. Model selection sets the floor&#xA;for your serving cost and the ceiling for your output quality at the same time, and the&#xA;two pull in opposite directions.&lt;/p&gt;&#xA;&lt;p&gt;This page frames the decision as an evaluation problem tied to your own task, not a&#xA;leaderboard comparison.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-you-will-learn&#34;&gt;What you will learn&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Which model properties actually affect serving cost.&lt;/li&gt;&#xA;&lt;li&gt;How to evaluate candidates against your own task rather than a public benchmark.&lt;/li&gt;&#xA;&lt;li&gt;How licensing and provenance constrain deployment options.&lt;/li&gt;&#xA;&lt;li&gt;When a smaller specialised model beats a larger general one.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;recommended-outline&#34;&gt;Recommended outline&lt;/h2&gt;&#xA;&lt;p&gt;This page is an outline. The subsections below are the planned structure;&#xA;they are filled in as the handbook is written.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Choosing the right GPU number</title>
      <link>https://ait.bsc.es/handbook/planning-your-deployment/choosing-the-right-gpu-number/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/handbook/planning-your-deployment/choosing-the-right-gpu-number/</guid>
      <description>&lt;p&gt;Accelerator count is driven by two independent requirements: fitting the model and its&#xA;KV cache in memory at all, and serving the expected concurrent load within your latency&#xA;targets. Either can dominate.&lt;/p&gt;&#xA;&lt;p&gt;This page separates the two questions so they can be sized independently and then&#xA;reconciled.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-you-will-learn&#34;&gt;What you will learn&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;How to separate the memory requirement from the throughput requirement.&lt;/li&gt;&#xA;&lt;li&gt;When to add accelerators to one replica versus adding replicas.&lt;/li&gt;&#xA;&lt;li&gt;How concurrency targets translate into hardware count.&lt;/li&gt;&#xA;&lt;li&gt;What headroom to leave for traffic variation.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;recommended-outline&#34;&gt;Recommended outline&lt;/h2&gt;&#xA;&lt;p&gt;This page is an outline. The subsections below are the planned structure;&#xA;they are filled in as the handbook is written.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Calculating GPU memory for serving LLMs</title>
      <link>https://ait.bsc.es/handbook/planning-your-deployment/calculating-gpu-memory/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/handbook/planning-your-deployment/calculating-gpu-memory/</guid>
      <description>&lt;p&gt;Running out of accelerator memory in production is one of the more common and more&#xA;avoidable inference failures. A memory budget computed in advance turns it into a&#xA;capacity decision rather than an incident.&lt;/p&gt;&#xA;&lt;p&gt;This page sets out the components of that budget and how each one scales.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-you-will-learn&#34;&gt;What you will learn&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The components that make up accelerator memory consumption.&lt;/li&gt;&#xA;&lt;li&gt;How to estimate weight memory from parameter count and precision.&lt;/li&gt;&#xA;&lt;li&gt;How KV cache size scales with batch size and context length.&lt;/li&gt;&#xA;&lt;li&gt;How much headroom to reserve for fragmentation and runtime overhead.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;recommended-outline&#34;&gt;Recommended outline&lt;/h2&gt;&#xA;&lt;p&gt;This page is an outline. The subsections below are the planned structure;&#xA;they are filled in as the handbook is written.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Choosing the right inference framework</title>
      <link>https://ait.bsc.es/handbook/planning-your-deployment/choosing-the-right-inference-framework/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/handbook/planning-your-deployment/choosing-the-right-inference-framework/</guid>
      <description>&lt;p&gt;Serving frameworks differ less in the features they list than in what they optimise for&#xA;and how they behave at the edges of their operating range. The right comparison is&#xA;against your own traffic pattern.&lt;/p&gt;&#xA;&lt;p&gt;This page gives the criteria to compare on, and a method for evaluating candidates&#xA;without committing to one first.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-you-will-learn&#34;&gt;What you will learn&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The criteria that meaningfully separate serving frameworks.&lt;/li&gt;&#xA;&lt;li&gt;Which optimizations to check for, and why their presence alone is not enough.&lt;/li&gt;&#xA;&lt;li&gt;How to benchmark candidates against your own traffic pattern.&lt;/li&gt;&#xA;&lt;li&gt;What operational characteristics to weigh alongside raw performance.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;recommended-outline&#34;&gt;Recommended outline&lt;/h2&gt;&#xA;&lt;p&gt;This page is an outline. The subsections below are the planned structure;&#xA;they are filled in as the handbook is written.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
