<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ollama on Fabian G. Williams</title><link>https://www.fabswill.com/tags/ollama/</link><description>Recent content in Ollama on Fabian G. Williams</description><image><title>Fabian G. Williams</title><url>https://www.fabswill.com/img/main/logo.jpg</url><link>https://www.fabswill.com/img/main/logo.jpg</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.fabswill.com/tags/ollama/index.xml" rel="self" type="application/rss+xml"/><item><title>Qwen 3.6 vs gpt-oss:120b on M3 Max: I Ran a Harder Test, the 8× Speed Gap Surprised Me</title><link>https://www.fabswill.com/blog/qwen-3-6-vs-gpt-oss-m3-max-8x-speed-gap-receipts/</link><pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate><guid>https://www.fabswill.com/blog/qwen-3-6-vs-gpt-oss-m3-max-8x-speed-gap-receipts/</guid><description>I published a Qwen 3.6 vs gpt-oss migration story, then ran an un-gameable eval against both on the same M3 Max. The receipts changed the speed narrative — gpt-oss:120b ran 8 to 11 times faster than qwen3.6:27b at parity reasoning quality. Here is the methodology and the data.</description></item><item><title>Replacing gpt-oss:120b With Qwen3.6 on a MacBook Pro: A Two-Day Local Model Benchmark</title><link>https://www.fabswill.com/blog/replacing-gpt-oss-with-qwen3-6-on-macbook-pro/</link><pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate><guid>https://www.fabswill.com/blog/replacing-gpt-oss-with-qwen3-6-on-macbook-pro/</guid><description>Two days benchmarking three Qwen3.6 variants against gpt-oss:120b on an M3 Max. A 21 GB coding-tuned model ran an OpenClaw-shaped research-brief workload 10x faster than gpt-oss — fast enough to seriously consider moving the work off SaaS frontier APIs. Plus the silent-hallucination trap I almost shipped through.</description></item></channel></rss>