Aller au contenu
Menu
Français

RAG vs Fine-tuning

Retrieval-Augmented Generation: ground a model answer in documents fetched at query time.

Comparaison des critères

Aucun attribut comparable n'a encore été enregistré pour ces deux technologies.

Lequel choisir ?

Généré à partir des différences ci-dessus par des règles structurées, et non par un modèle.

Choose RAG if…

Aucun des attributs enregistrés ne le distingue à son avantage.

Choose Fine-tuning if…

Aucun des attributs enregistrés ne le distingue à son avantage.

À propos de cette page

La page reste accessible mais est exclue des index de recherche tant qu'elle ne contient pas assez de détails sourcés (PRD SEO-08).

RAG

technique · Techniques

Retrieval-Augmented Generation answers a question by first retrieving relevant passages from a knowledge source and then having a language model compose the answer from them. It solves two problems at once: a model cannot know facts outside its training data, and fine-tuning it on new facts is expensive and must be repeated whenever the facts change. It exists because most factual answers are cheaper to look up than to memorise. The cost is a new dependency chain - embeddings, a vector store, reranking and a generation step - which is why it is the most interconnected node in this graph.

Fine-tuning

technique · Techniques

Fine-tuning continues training an already pre-trained model on a smaller, task-specific dataset so that its weights shift toward the behaviour you want. It solves the problem that a general model may not follow a house style, a domain vocabulary or a fixed output format. It exists because pre-training is expensive but adaptation is not: starting from a pre-trained checkpoint means a modest dataset is enough. It is the main alternative to retrieval when the goal is behaviour rather than fresh facts.