Home / Companies / Lightning AI / Blog / Post Details
Content Deep Dive

Finetuning LLMs with LoRA and QLoRA: Insights from Hundreds of Experiments

Blog post from Lightning AI

Post Details
Company
Date Published
Author
Sebastian Raschka
Word Count
3,258
Company Posts That Month
7
Language
English
Hacker News Points
-
Post removed?
No
Summary

An experimental study of LoRA instruction fine-tuning used the Alpaca dataset, Llama 2 7B, and several language, factual, truthfulness, and arithmetic benchmarks to examine optimizer, quantization, training-duration, and adapter-hyperparameter choices on a single A100 GPU. QLoRA reduced peak GPU memory from about 21 GB to 14 GB but increased training time by roughly 30% and caused modest performance trade-offs, while replacing AdamW with SGD yielded little memory benefit at low LoRA ranks because relatively few adapter parameters were trainable. A cosine learning-rate scheduler improved some truthfulness and factual metrics, but training for two passes over the dataset generally degraded results, particularly arithmetic, likely because Alpaca contains limited arithmetic content. Expanding LoRA from attention components to all applicable layers and increasing rank improved results only when the alpha scaling parameter was adjusted proportionally; the strongest reported configuration used rank 256 and alpha 512, although very large ranks performed worse or failed to converge. The final leaderboard comparison found that tuned QLoRA improved several benchmarks over the base model but not all, underscoring that dataset selection, alignment methods, and evaluation diversity remain important alongside LoRA settings.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
AI Model Fine-tuning 79 659 128 71 +15%
LLM 11 3,179 314 123 +28%
Reinforcement learning 2 98 21 16 +63%
AI Guardrails 1 92 42 22 +24%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.