Equation 36 · Naive, Graph, and Agentic: A Systems Comparison of RAG Architectures
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
This equation states an equality: the expressions on both sides have the same value under the article’s assumptions. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol L_total
otal is part of the quantity the equation computes from the expression on the right.
Symbol i
i appears in the bound of this sum. The bound states where the repeated operation starts, ends, or which values it includes.
Symbol k
k appears in the bound of this sum. The bound states where the repeated operation starts, ends, or which values it includes.
Symbol L_retrieve^(i)
etrieve^(i) is one of the signed contributions combined to compute the quantity on the left.
Symbol L_LLM^(i)
LM^(i) is one of the signed contributions combined to compute the quantity on the left.
=
The expressions on both sides represent the same quantity under the stated assumptions.
See an illustrated explanation →subscript
The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.
superscript
A raised number can be a power. When it is a label or bound, it selects a case or the upper limit of a sum; the formula’s structure distinguishes these uses.
See an illustrated explanation →Starting index or lower bound: i=1
This label says where the repeated addition, multiplication, or accumulation starts. Read its value or condition together with the article’s description of the index.
Ending index or upper bound: k
This label says where the repeated addition, multiplication, or accumulation stops. It sets the last term or end of the range.
How to interpret it
Read it with the definitions, units, and assumptions supplied by the article.
What the article says around this equation
A single latency model makes the difference between the first three rows and the last two concrete. Writing for query encoding, and and for the retrieval and generation cost of round i , . For naive and hybrid RAG, k = 1 by construction — the sum has exactly one term, and total latency is boundable in advance for any query. For iterative RAG, k is a small integer set by a heuristic or a step cap chosen by the system builder, so the worst case is known even though the typical case varies with question difficulty. For agentic RAG, k is a random variable generated by the policy itself at run time, and its…
Read the full surrounding passage
A single latency model makes the difference between the first three rows and the last two concrete. Writing for query encoding, and and for the retrieval and generation cost of round i , . For naive and hybrid RAG, k = 1 by construction — the sum has exactly one term, and total latency is boundable in advance for any query. For iterative RAG, k is a small integer set by a heuristic or a step cap chosen by the system builder, so the worst case is known even though the typical case varies with question difficulty. For agentic RAG, k is a random variable generated by the policy itself at run time, and its distribution is exactly what the operator does not control without adding an external cap. The same formula describes all five families; what changes is only where k comes from, and that difference is the whole of the engineering distinction between “a pipeline with a loop in it” and “a policy that decides how much to loop.”
Sources cited in the article section
- [7] Interleaving Retrieval with Chain-of-Thought Reasoning for Knowledge-Intensive Multi-Step Questions ↗
- [4] From Local to Global: A Graph RAG Approach to Query-Focused Summarization ↗
- [9] Self-RAG: Learning to Retrieve, Generate, and Critique through Self-Reflection ↗
These citations give research context. Read each source to check which claims it supports.
Return to Naive, Graph, and Agentic: A Systems Comparison of RAG Architectures