---
title: "Comment by Kartik N V J K on \"Why Chunking Strategy Can Make or Break Your RAG Pipeline\" | Hashnode"
description: "Chunking is the least glamorous and most decisive knob in RAG, agreed. What finally worked for me was chunking on document structure instead of a fixed token co"
url: "https://hashnode.com/posts/why-chunking-strategy-can-make-or-break-your-rag-pipeline/6a7ab6663ddc972e303c1f03/comment/6a7b551942d6c75df9575550"
---

[Discussion](https://hashnode.com/posts/why-chunking-strategy-can-make-or-break-your-rag-pipeline/6a7ab6663ddc972e303c1f03)

Comment [Why Chunking Strategy Can Make or Break Your RAG Pipeline](https://hashnode.com/posts/why-chunking-strategy-can-make-or-break-your-rag-pipeline/6a7ab6663ddc972e303c1f03)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Aug 11](https://hashnode.com/posts/why-chunking-strategy-can-make-or-break-your-rag-pipeline/6a7ab6663ddc972e303c1f03/comment/6a7b551942d6c75df9575550)

Chunking is the least glamorous and most decisive knob in RAG, agreed. What finally worked for me was chunking on document structure instead of a fixed token count, then scoring retrieval against a labeled set so chunk size became a measured decision and not a guess. Are you tuning chunk size by eye, or do you have a retrieval metric you watch when you change it?

[Ajitabh Singh](https://hashnode.com/@ajitabh)

[Aug 11](https://hashnode.com/posts/why-chunking-strategy-can-make-or-break-your-rag-pipeline/6a7ab6663ddc972e303c1f03/comment/6a7b551942d6c75df9575550#reply-6a7b8266b2f61ffc0969b0b6)

Absolutely agree. I don't think chunk size should be tuned by eye. My recommendation is to align chunks with the document's natural structure first, then compare strategies using retrieval metrics like Recall@K, Precision@K, and MRR on a representative query set. The key point for me is that chunk size is a workload-dependent decision, not a universal number.