<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vllm on ZoliBen Csupra(Kabra)</title>
    <link>https://zoliben.com/en/tags/vllm/</link>
    <description>Recent content in Vllm on ZoliBen Csupra(Kabra)</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 18 Aug 2026 12:00:00 +0000</lastBuildDate>
    <atom:link href="https://zoliben.com/en/tags/vllm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MTP vs prompt caching — Qwen3.8-27B-FP8 on 2× H100: which one should you run?</title>
      <link>https://zoliben.com/en/posts/2026-08-18-qwen-mtp-vs-prefix-cache-h100/</link>
      <pubDate>Tue, 18 Aug 2026 12:00:00 +0000</pubDate>
      <guid>https://zoliben.com/en/posts/2026-08-18-qwen-mtp-vs-prefix-cache-h100/</guid>
      <description>&lt;p&gt;Running Qwen3.8-27B-FP8 on two H100s, MTP speculative decoding was the biggest decode win (49 → 95 tok/s). But there&amp;rsquo;s a catch: in vLLM, &lt;strong&gt;MTP and prefix caching are mutually exclusive&lt;/strong&gt;. So the question became: which config should actually go into production?&lt;/p&gt;&#xA;&lt;p&gt;The answer came from running the two configs head-to-head: &lt;strong&gt;GPU0 no-MTP + prefix caching&lt;/strong&gt;, &lt;strong&gt;GPU1 MTP&lt;/strong&gt; (3 draft tokens). Both are TP1, 262K max context, FP8 KV cache, with a LiteLLM proxy load-balancing between them. All numbers are TTFT p50 unless noted.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
