<?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>Rag on IT Comparison</title><link>https://comparison.metacog.co.kr/tags/rag/</link><description>Recent content in Rag on IT Comparison</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 03 Aug 2026 03:44:47 +0900</lastBuildDate><atom:link href="https://comparison.metacog.co.kr/tags/rag/index.xml" rel="self" type="application/rss+xml"/><item><title>Fine-Tuning vs RAG: Updating Model Weights vs Retrieving External Knowledge</title><link>https://comparison.metacog.co.kr/posts/2026-08-03-fine-tuning-vs-rag-updating-model-weights-vs-retrieving-exte/</link><pubDate>Mon, 03 Aug 2026 03:44:47 +0900</pubDate><guid>https://comparison.metacog.co.kr/posts/2026-08-03-fine-tuning-vs-rag-updating-model-weights-vs-retrieving-exte/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;Fine-tuning and RAG (Retrieval-Augmented Generation) are two ways to make a large language model produce better, more relevant answers, but they intervene at different points in the pipeline. Fine-tuning permanently adjusts the model&amp;rsquo;s &lt;strong class="kw"&gt;weights&lt;/strong&gt; through additional training, while RAG leaves the model untouched and instead injects context by &lt;strong class="kw"&gt;retrieving&lt;/strong&gt; documents at query time. The choice matters because it determines how you update knowledge, control latency and cost, and trace where an answer came from.&lt;/p&gt;</description></item></channel></rss>