<?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 Hullabalooing</title>
    <link>https://cruver.ai/tags/vllm/</link>
    <description>Recent content in Vllm on Hullabalooing</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 02 Mar 2026 00:00:00 -0700</lastBuildDate>
    <atom:link href="https://cruver.ai/tags/vllm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I Pushed Local LLMs Harder. Here&#39;s What Two Models Actually Did.</title>
      <link>https://cruver.ai/gpu-ai/posts/local-llm-two-models-real-project/</link>
      <pubDate>Mon, 02 Mar 2026 00:00:00 -0700</pubDate>
      <guid>https://cruver.ai/gpu-ai/posts/local-llm-two-models-real-project/</guid>
      <description>&lt;p&gt;In Part 1 of this series, I set up Claude Code against local LLMs on dual MI60 GPUs and watched it scaffold a Flask application from scratch. Small tasks worked. Complex ones did not. I ended with three ideas I wanted to test: running a dense model, trying Claude Code&amp;rsquo;s agent teams feature, and building a persistent memory layer for coding sessions.&lt;/p&gt;&#xA;&lt;p&gt;I started the experiment that mattered most: giving a local LLM a project with real scope and seeing what happened. I ran the same project against two different models. The results were instructive, and not in the direction I expected.&lt;/p&gt;</description>
    </item>
    <item>
      <title>I Ran Claude Code on Local LLMs for a Month. Here&#39;s What Worked for Me.</title>
      <link>https://cruver.ai/gpu-ai/posts/claude-code-local-llms-what-worked/</link>
      <pubDate>Mon, 16 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://cruver.ai/gpu-ai/posts/claude-code-local-llms-what-worked/</guid>
      <description>&lt;p&gt;I have been running local LLMs on dual AMD MI60 GPUs for over a year, and recently pointed Claude Code at them to see how close I could get to frontier-quality agentic coding on my own hardware. I wanted to know: how close can local models actually get to Anthropic&amp;rsquo;s Claude for building real software?&lt;/p&gt;&#xA;&lt;p&gt;This is the first post in a series documenting that experiment. Future posts will cover specific agentic coding sessions, hardware and model setup, and the tools I am building to close the gap.&lt;/p&gt;</description>
    </item>
    <item>
      <title>vLLM Inference on MI60</title>
      <link>https://cruver.ai/gpu-ai/posts/vllm-inference-mi60/</link>
      <pubDate>Wed, 21 Jan 2026 00:00:00 -0700</pubDate>
      <guid>https://cruver.ai/gpu-ai/posts/vllm-inference-mi60/</guid>
      <description>&lt;p&gt;Production inference using vLLM with tensor parallelism across dual MI60 GPUs.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-vllm&#34;&gt;Why vLLM?&lt;a class=&#34;anchor&#34; href=&#34;#why-vllm&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;After evaluating Ollama, llama.cpp, and vLLM for MI60 inference, &lt;strong&gt;vLLM&lt;/strong&gt; emerged as the best choice:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tensor Parallelism&lt;/strong&gt;: Native support for splitting large models across multiple GPUs. With dual MI60s (64GB total), I can run 70B parameter models that wouldn&amp;rsquo;t fit on a single GPU.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;PagedAttention&lt;/strong&gt;: More efficient memory management, allowing higher GPU utilization (90%) without OOM errors.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Running Claude Code with Local LLMs via vLLM and LiteLLM</title>
      <link>https://cruver.ai/gpu-ai/posts/claude-code-local-llms-1768966311/</link>
      <pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://cruver.ai/gpu-ai/posts/claude-code-local-llms-1768966311/</guid>
      <description>&lt;p&gt;Every query to Claude Code means sending my source code to Anthropic&amp;rsquo;s servers. For proprietary codebases, that&amp;rsquo;s a non-starter. With vLLM and LiteLLM, I can point Claude Code at my own hardware - keeping my code on my network while maintaining the same workflow.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-architecture&#34;&gt;The Architecture&lt;a class=&#34;anchor&#34; href=&#34;#the-architecture&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The trick is that Claude Code expects the Anthropic Messages API, but local inference servers speak OpenAI&amp;rsquo;s API format. LiteLLM bridges this gap. It accepts Anthropic-formatted requests and translates them to OpenAI format for my local vLLM instance.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
