Chunking Strategies for RAG, Measured
Chunking is how a retrieval-augmented generation (RAG) system cuts its documents into the pieces it searches. When a question comes in, the system embeds it (turns it into a vector, a list of numbers that places similar meanings close together), finds the nearest chunks, and hands those to the model as context. The model can only answer from what it is handed, so the cut decides the ceiling on every answer before any model runs.
This post opens a series that builds one retrieval system over this blog, one layer per post. The corpus is the 23 posts published before this one, about 31,600 words, and the test is 80 questions written in a reader's words, each with the exact passage that answers it. Six chunking strategies were run against the same questions with the same embedding model. Cutting every 200 words put the answering passage in the top five results for 73.8% of questions. Searching 50-word pieces and returning the 200-word section around them reached 95.0%, the same as sending whole posts, while sending a ninth as many words.
In the full article
What it covers
- How the Measurement Works
- Why Not Send Whole Posts?
- Six Ways to Cut a Document
- The Results at 200 Words
- What Overlap Buys
- Bigger Chunks Are Not Safer
- The Parent-Child Dial
- When You Do Not Need It
- Key Takeaways
- Sources
The full article is on Bliztek, LLC Blog, my web development company's blog. This page is the summary.
- Read time
- 9 min
- Sections
- 10
