<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rocm on Hullabalooing</title>
    <link>https://cruver.ai/tags/rocm/</link>
    <description>Recent content in Rocm 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/rocm/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>ComfyUI on MI60</title>
      <link>https://cruver.ai/gpu-ai/posts/comfyui-mi60/</link>
      <pubDate>Wed, 21 Jan 2026 00:00:00 -0700</pubDate>
      <guid>https://cruver.ai/gpu-ai/posts/comfyui-mi60/</guid>
      <description>&lt;p&gt;Node-based Stable Diffusion UI with AMD MI60 GPU acceleration via ROCm.&lt;/p&gt;&#xA;&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;a class=&#34;anchor&#34; href=&#34;#overview&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;ComfyUI runs as a containerized service using a custom ROCm 5.7 image built for the MI60&amp;rsquo;s gfx906 architecture. It can run standalone on both GPUs or alongside vLLM in the &lt;code&gt;image-chat&lt;/code&gt; configuration.&lt;/p&gt;&#xA;&lt;h2 id=&#34;quick-start&#34;&gt;Quick Start&lt;a class=&#34;anchor&#34; href=&#34;#quick-start&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#e2e4e5;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#78787e&#34;&gt;# Build the container image&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ff5c57&#34;&gt;cd&lt;/span&gt; comfyui&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;make build&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#78787e&#34;&gt;# Start ComfyUI (standalone, both GPUs)&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;make up&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#78787e&#34;&gt;# Or use the image-chat config (vLLM on GPU0, ComfyUI on GPU1)&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;curl -X POST -H &lt;span style=&#34;color:#5af78e&#34;&gt;&amp;#34;Content-Type: application/json&amp;#34;&lt;/span&gt; &lt;span style=&#34;color:#5af78e&#34;&gt;\&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  -d &lt;span style=&#34;color:#5af78e&#34;&gt;&amp;#39;{&amp;#34;config&amp;#34;:&amp;#34;image-chat&amp;#34;}&amp;#39;&lt;/span&gt; http://localhost:9100/switch&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Access the UI at &lt;a href=&#34;http://localhost:8188&#34;&gt;http://localhost:8188&lt;/a&gt;.&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>
  </channel>
</rss>
