AI Model Wiki

    Skip to main content
    15 min read
    Lesson 1 of 5

    Why Fine-Tune? When Prompting Isn't Enough

    From the course Fine-Tuning AI Models: LoRA, QLoRA & Beyond

    Fine-tuning is the process of taking a pre-trained model and continuing its training on a smaller, domain-specific dataset. It's the bridge between a general-purpose model and one that excels at your exact task.

    When to Fine-Tune vs. Prompt Engineer

    Prompt engineering is your first tool — it's fast, cheap, and requires no infrastructure. But it has limits:

    • Consistent formatting: If you need every response in a precise JSON schema or specific tone, fine-tuning bakes this into the model's weights rather than relying on instructions.
    • Domain knowledge: Medical, legal, or highly technical domains where the base model lacks depth benefit enormously from fine-tuning on curated examples.
    • Latency & cost: Fine-tuned models can produce correct outputs with shorter prompts, reducing token costs and response time.
    • Proprietary style: If you need outputs that match a specific brand voice across thousands of interactions, fine-tuning learns patterns that prompts can only approximate.

    The Fine-Tuning Spectrum

    Not all fine-tuning is equal. The field has evolved from full fine-tuning (updating every parameter) to increasingly efficient methods:

    MethodParameters UpdatedGPU MemoryTraining Time
    Full fine-tuning100%Very highHours-days
    LoRA0.1-1%ModerateMinutes-hours
    QLoRA0.1-1% (quantized)LowMinutes-hours
    Prompt tuning<0.01%Very lowMinutes

    Key Terminology

    • Base model: The pre-trained model you start from (e.g., Llama 3, Mistral, Gemma)
    • Adapter: Small trainable matrices added to the frozen base model
    • Epoch: One complete pass through your training dataset
    • Loss: A number measuring how wrong the model's predictions are — lower is better
    • Overfitting: When the model memorizes training data instead of learning patterns

    Key Takeaways

    • •Fine-tune when prompt engineering can't achieve consistent formatting, domain knowledge, or style requirements
    • •Parameter-efficient methods like LoRA update <1% of parameters with comparable results
    • •Always try prompting and RAG before investing in fine-tuning
    • •Understanding the cost-quality tradeoff is essential for choosing the right approach
    0 of 5 lessons marked complete

    Progress is kept in this browser only.