← Back to article

Equation 18 · Naive, Graph, and Agentic: A Systems Comparison of RAG Architectures

What does this equation mean?

cquery(Q)=CindexQ+cmarginal.c_{\text{query}}(Q) = \frac{C_{\text{index}}}{Q} + c_{\text{marginal}}.

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.

Start withC_index
Divide byQ
This relates toc_query(Q)
How to read the two sides of this formula. Follow the article passage for the meaning of each quantity.

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

cqueryc_{\text{query}}

Symbol c_query

cqc_query is part of the quantity the equation computes from the expression on the right.

Understand this part →

QQ

Symbol Q

the when.

Understand this part →

CindexC_{\text{index}}

Symbol C_index

the writing.

Understand this part →

cmarginalc_{\text{marginal}}

Symbol c_marginal

cmc_marginal is one of the signed contributions combined to compute the quantity on the left.

Understand this part →

=

=

The expressions on both sides represent the same quantity under the stated assumptions.

Understand this part →

See an illustrated explanation →
fraction

fraction

Divide the expression above the line by the one below it.

Understand this part →

See an illustrated explanation →
addition

addition

Add the term after the plus sign to the term or group before it.

Understand this part →

subscript

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.

Understand this part →

How to interpret it

With a fixed numerator, increasing a nonzero denominator reduces the fraction. Read it with the definitions, units, and assumptions supplied by the article.

What the article says around this equation

This is the one family among the five whose defining engineering trade-off is temporal rather than architectural: cost is shifted from query time to index time. Writing CindexC_{\text{index}} for the one-time cost of building the graph and its community summaries, and cmarginalc_{\text{marginal}} for the cost of answering a single query against the finished structure, the amortised cost of a query workload of size Q against one graph is cquery(Q)=CindexQ+cmarginalc_{\text{query}}(Q) = \frac{C_{\text{index}}}{Q} + c_{\text{marginal}}. When Q is small — a corpus queried rarely, or one still being explored — CindexC_{\text{index}} dominates and the naive or hybrid architectures are cheaper by a wide margin, because they pay nothing until a query arrives. When Q is large against a stable…
Read the full surrounding passage
This is the one family among the five whose defining engineering trade-off is temporal rather than architectural: cost is shifted from query time to index time. Writing CindexC_{\text{index}} for the one-time cost of building the graph and its community summaries, and cmarginalc_{\text{marginal}} for the cost of answering a single query against the finished structure, the amortised cost of a query workload of size Q against one graph is cquery(Q)=CindexQ+cmarginalc_{\text{query}}(Q) = \frac{C_{\text{index}}}{Q} + c_{\text{marginal}}. When Q is small — a corpus queried rarely, or one still being explored — CindexC_{\text{index}} dominates and the naive or hybrid architectures are cheaper by a wide margin, because they pay nothing until a query arrives. When Q is large against a stable corpus, the fixed term is driven down toward zero and the comparison turns on cmarginalc_{\text{marginal}} against the per-query cost of the alternatives. The direction of that comparison depends on the question being asked, not only on volume: Edge and colleagues report that GraphRAG produces substantially more comprehensive and diverse answers than a conventional RAG baseline specifically on query-focused summarisation over large corpora, the kind of question — “what are the main themes across this entire collection” — that a top- k chunk retriever structurally cannot answer well no matter how many times it is queried, because no fixed small set of chunks represents a corpus-wide theme [ 4 ] .

Read the equation in its article →

Sources cited in the surrounding passage

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

See this formula across 1 published context →

Browse the mathematical compendium →