<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>llms on franfabrizio.dev</title>
    <link>http://franfabrizio.dev/tags/llms/</link>
    <description>Recent content in llms on franfabrizio.dev</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 -0500</lastBuildDate>
    <atom:link href="http://franfabrizio.dev/tags/llms/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Adventures in Local LLMs Part 4: Choosing a Model for Your Setup</title>
      <link>http://franfabrizio.dev/posts/adventures-in-local-llms-part-4/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 -0500</pubDate>
      <guid>http://franfabrizio.dev/posts/adventures-in-local-llms-part-4/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;In &lt;a href=&#34;http://franfabrizio.dev/posts/adventures-in-local-llms-part-3/&#34;&gt;Part 3&lt;/a&gt;, I walked through the software stack I ended up running — Ollama, Open WebUI, paperless-gpt, and a handful of other tools — and how much of it felt like a science experiment. The stack worked, mostly, but it was only half the equation. The other half is the model itself.&lt;/p&gt;&#xA;&lt;p&gt;Once you&amp;rsquo;ve got your hardware constraints figured out (we covered those exhaustively in &lt;a href=&#34;http://franfabrizio.dev/posts/adventures-in-local-llms-part-2/&#34;&gt;Part 2&lt;/a&gt;) and your software stack in place, you&amp;rsquo;re left with a deceptively simple question: &lt;em&gt;which model do you actually run?&lt;/em&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
