<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>holler</title><link>/holler/</link><atom:link href="/holler/index.xml" rel="self" type="application/rss+xml"/><description>Field notes from a small local-inference fleet: AMD 7900 XTX on Vulkan, llama.cpp, llama-swap, and burst cloud pods for frontier models. Measured, not vibes.</description><language>en-us</language><lastBuildDate>Sun, 11 Oct 2026 21:40:10 +0000</lastBuildDate><item><title>Flash-Next Q2 on Strata, on an AMD card: how it became my daily driver</title><link>/holler/posts/flashnext-q2-strata-amd-daily-driver/</link><guid>/holler/posts/flashnext-q2-strata-amd-daily-driver/</guid><description>A config flag made a paid seat look like it was degrading at long context. Sorting that out is what made a 176B mixture-of-experts model on one 24 GB AMD card my daily driver.</description><pubDate>Sun, 11 Oct 2026 00:00:00 +0000</pubDate><category>strata</category><category>amd</category><category>rdna3</category><category>flash-next</category><category>qwen</category><category>quantization</category><category>context</category><category>local-llm</category></item><item><title>Seven weeks of Qwen 3.8: marking the milestone with Qwen 4 on the horizon</title><link>/holler/posts/qwen38-seven-weeks/</link><guid>/holler/posts/qwen38-seven-weeks/</guid><description>The 3.8 base ties the strongest fine-tune on the roster within measured noise; the peak — 0.931 — is a configuration, not a download.</description><pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate><category>qwen3.8</category><category>qwen4</category><category>llama.cpp</category><category>spec-decode</category><category>quantization</category><category>fine-tune</category></item><item><title>Turning on a speed feature dropped my hard-reasoning scores from 39/40 to 0/40</title><link>/holler/posts/spec-decode-quantized-targets-degradation/</link><guid>/holler/posts/spec-decode-quantized-targets-degradation/</guid><description>An A/B test reveals that enabling draft-MTP speculative decoding on a Q4_K_M 27B model silently collapses long-chain reasoning performance, matching an upstream bug class.</description><pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate><category>llama.cpp</category><category>speculative-decoding</category><category>quantization</category><category>quality-evaluation</category></item><item><title>One session, 1.9M tokens, idea to launch</title><link>/holler/posts/qwen38-27b-long-session-launch/</link><guid>/holler/posts/qwen38-27b-long-session-launch/</guid><description>One continuous local-27B session took a coding-agent TUI from a closed research handoff to a launched build — long-horizon work without a frontier model or a million-token context.</description><pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate><category>local-llm</category><category>qwen</category><category>agent-harness</category><category>long-context</category><category>compaction</category></item><item><title>A 9B I told to log a bug went and found it instead</title><link>/holler/posts/ornith-9b-bug-hunt/</link><guid>/holler/posts/ornith-9b-bug-hunt/</guid><description>An Ornith-1.5-9B I installed to cover a gap while the big box was down answered real infra questions in short bursts — and, told to &amp;ldquo;log a bug,&amp;rdquo; went on a root-cause hunt that nearly fixed it before the context ceiling killed the run.</description><pubDate>Fri, 11 Sep 2026 00:00:00 +0000</pubDate><category>ornith</category><category>agentic-rl</category><category>llama-cpp</category><category>inference-laptop</category><category>context-window</category></item><item><title>The GSQ 3-bit that carried four hundred thousand tokens</title><link>/holler/posts/qwen38-gsq-workday/</link><guid>/holler/posts/qwen38-gsq-workday/</guid><description>One working day running the GSQ-RCO 3-bit quant of Qwen3.8-27B as the daily coding agent across eight sessions: decode held, prefill paid, five sessions overflowed the box&amp;rsquo;s cram budget, and the honest verdict — not a step down, a little looser, and I&amp;rsquo;m reverting to the 4-bit tomorrow.</description><pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate><category>llama.cpp</category><category>qwen</category><category>quantization</category><category>gsq</category><category>llama-swap</category><category>amd</category><category>coding-agent</category></item><item><title>I paid $4 for a frontier model to defrag my agent's memory</title><link>/holler/posts/memory-defrag-dispatch/</link><guid>/holler/posts/memory-defrag-dispatch/</guid><description>Two headless dispatches to a rented 320B MoE rebuilt my coding agent&amp;rsquo;s drifted markdown memory — −21.5% standing context for about $4 of billed time — and the reusable part isn&amp;rsquo;t the defrag, it&amp;rsquo;s the dispatch contract.</description><pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate><category>agents</category><category>memory</category><category>headless-dispatch</category><category>runpod</category></item><item><title>Qwen3.8's thinking knob is not a volume knob</title><link>/holler/posts/qwen38-thinking-levels/</link><guid>/holler/posts/qwen38-thinking-levels/</guid><description>off / low / medium / xhigh on the same 27B model, same trap prompt, temp 0 — xhigh turns out to be a near-duplicate of default, the instruction-less &amp;lsquo;medium&amp;rsquo; thinks more than &amp;rsquo;low&amp;rsquo;, and no level drifted off the right answer.</description><pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate><category>llama.cpp</category><category>qwen</category><category>reasoning</category><category>thinking-models</category><category>amd</category><category>rdna3</category></item><item><title>The 3-bit model ran all day. It didn't break. But it kept trying to edit the same broken line.</title><link>/holler/posts/qwen38-gsq-production-day/</link><guid>/holler/posts/qwen38-gsq-production-day/</guid><description>After a week of benching, the 3-bit quant finally carried real traffic — and its quirks were weirder than the numbers suggested.</description><pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate><category>llama.cpp</category><category>qwen</category><category>quantization</category><category>llama-swap</category><category>amd</category></item><item><title>A kill→respawn race left my 7900 XTX serving at CPU speed for 2.5 hours</title><link>/holler/posts/xtx-cpu-fallback-incident/</link><guid>/holler/posts/xtx-cpu-fallback-incident/</guid><description>llama-swap&amp;rsquo;s hot reload killed my 27B server; the respawn six seconds later landed on the dying server&amp;rsquo;s VRAM residue and llama.cpp silently fell back to CPU. Nothing errored. Here&amp;rsquo;s the failure, the A/B proof, and the 9-second probe I now run after every deploy.</description><pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate><category>llama.cpp</category><category>llama-swap</category><category>vulkan</category><category>amd</category><category>rdna3</category><category>troubleshooting</category></item></channel></rss>