<?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 Experiment, Fail, Learn, Repeat</title>
    <link>https://www.hairizuan.com/tags/vllm/</link>
    <description>Recent content in Vllm on Experiment, Fail, Learn, Repeat</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 Hairizuan Noorazman</copyright>
    <lastBuildDate>Sun, 01 Nov 2026 18:34:23 +0800</lastBuildDate><atom:link href="https://www.hairizuan.com/tags/vllm/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Serving Gemma Across Two Nodes with vLLM and LeaderWorkerSet, on CPU</title>
      <link>https://www.hairizuan.com/serving-gemma-across-two-nodes-with-vllm-and-leaderworkerset-on-cpu/</link>
      <pubDate>Wed, 28 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.hairizuan.com/serving-gemma-across-two-nodes-with-vllm-and-leaderworkerset-on-cpu/</guid>
      <description>&lt;p&gt;I wanted to try two things at once: Kubernetes&amp;rsquo; &lt;code&gt;LeaderWorkerSet&lt;/code&gt; (LWS), the API for running a group of pods as one unit, and vLLM&amp;rsquo;s multi-node serving. The cheapest way to exercise both is not a GPU cluster. It is two small CPU nodes, one small model, and a deliberate decision to split that model across the nodes even though it fits on one.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
