Grouped Value Attention matches GQA on a 47% smaller KV cache

1 hour ago

A chat model keeps a store of numbers for every word it has already read. That store is the KV cache, and it fills GPU memory in a long chat. For each word the cache holds a key, which the model matches against, and a value, the content it pulls out. Grouped Value Attention keeps the values and drops the keys. When the model needs a key, it rebuilds that key from the value. The paper's Figure 1 draws both designs. On the left, grouped-query attention stores keys and values. On the right, Grouped Value Attention stores values only.

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00Grouped Value Attention caches the values and rebuilds the keys
  2. 0:30Grouped Value Attention ties GQA accuracy with a cache 47 percent smaller
  3. 1:06A learned map rebuilds each key, and the query absorbs the map
  4. 1:38Using each value as its own key halved the cache and trailed GQA
  5. 2:05A small shared position key keeps word order without storing full keys
  6. 2:49Rebuilt keys started far smaller than queries and flattened attention
  7. 3:15Grouped Value Attention scores 44.35 percent against GQA 44.36 percent
  8. 3:58The 47 percent saving counts stored numbers and has no timing yet
  9. 4:43Skim it
Show transcript

Grouped Value Attention caches the values and rebuilds the keys

Figure 1 · grouped-query attention · keys and values cached
Figure 1 · Grouped Value Attention · values cached
values only
Grouped Value Attention caches the values and rebuilds the keys
About 45 to 47 percent fewer cached numbers than GQA at 350 million parameters
Tripathi, Kumar, Khan · FrontiersMind · “Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction” · arXiv 2609.13285 · Sep 2026

A chat model keeps a store of numbers for every word it has already read. That store is the KV cache, and it fills GPU memory in a long chat. For each word the cache holds a key, which the model matches against, and a value, the content it pulls out. Grouped Value Attention keeps the values and drops the keys. When the model needs a key, it rebuilds that key from the value. The paper's Figure 1 draws both designs. On the left, grouped-query attention stores keys and values. On the right, Grouped Value Attention stores values only.

Grouped Value Attention ties GQA accuracy with a cache 47 percent smaller

Grouped Value Attention ties GQA’s accuracy with a cache 47 percent smaller
About 350 million parameters · five reasoning quizzes · three runs each
GQA
100
Grouped Value Attention
53
cached numbers per token, GQA = 100
built from the paper’s Eq. 13 and stated savings · a count, not measured memory
average accuracy GQA 44.36 Grouped Value Attention 44.35
Tripathi, Kumar, Khan · FrontiersMind · “Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction” · arXiv 2609.13285 · Sep 2026

Each new word asks a question, called the query. The model scores that query against every stored key, then pulls in the values whose keys match best. A model asks many of those questions at once, one per attention head. Grouped-query attention, or GQA, lets several heads share one stored key and one stored value. On models of about 350 million parameters, the paper counts a Grouped Value Attention cache 47 percent smaller than GQA's. On five reasoning quizzes, Grouped Value Attention averages 44.35 percent accuracy. GQA averages 44.36 percent.

A learned map rebuilds each key, and the query absorbs the map

A learned map rebuilds each key, and the query absorbs the map
Every head gets its own key · GQA heads in a group share one
q (v M)T = (q MT) vT
Eq. 7 · the paper calls it exact
Drawn as narrated
stored value
times the map
folded into the query
Figure 1 · Grouped Value Attention panel, unaltered
Tripathi, Kumar, Khan · FrontiersMind · “Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction” · arXiv 2609.13285 · Sep 2026

In Grouped Value Attention, each head owns a small grid of learned numbers, called a map. Multiply a stored value by the map, and out comes that head's key. Scoring then multiplies the query by that rebuilt key. The map stays fixed once training ends. So the model can multiply the query by the map once, and score the query straight against the stored value. Equation 7 in the paper shows both routes give the same score, and the authors call the identity exact. The cache holds values only. Each head also gets its own key. In GQA, every head in a group shares one key.

Using each value as its own key halved the cache and trailed GQA

Using each value as its own key halved the cache and trailed GQA
Training error stays above GQA for the whole plotted stretch
Figure 3 · unaltered
In the margin
shared KV (pink) · GQA baseline (orange)
plot ends near 4.4 billion of 30 billion tokens
Tripathi, Kumar, Khan · FrontiersMind · “Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction” · arXiv 2609.13285 · Sep 2026

The team tried a simpler cut first. They used each stored value as its own key, with no map. That version also halves the cache. Figure 3 plots its training error, how often the model guesses the next token wrong. Tokens are the word pieces a model reads. The error stays above GQA for the whole stretch the figure plots, the first 4.4 billion tokens of a 30 billion-token run. The gap narrows by the end of the plot. The map gives each key room to differ from its value.

A small shared position key keeps word order without storing full keys

A small shared position key keeps word order without storing full keys
Borrowed from DeepSeek-V2’s MLA · 47 percent saved at 16 numbers, 45 percent at 24
content key = v M
position key = rotated, shared by all heads, cached
score = content part + position part
Eqs. 8 to 10 · decoupled rotation
In the margin
folds into the query
stored · 16 or 24 numbers per token
Tripathi, Kumar, Khan · FrontiersMind · “Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction” · arXiv 2609.13285 · Sep 2026

Word order breaks the shortcut. Models mark word order by rotating the query and the key by an angle. That angle depends on how far apart the two words sit. This rotation is called RoPE, and it lands between the query and the map. The angle changes for every pair of words, so the map can no longer move onto the query once. The fix comes from MLA, DeepSeek-V2's attention design, another way to shrink the cache. Each head splits in two. The content part rebuilds its key from the value, without rotation, so the fold still works. A small position part carries the rotation. Its key is shared by every head and stored, 16 or 24 numbers per token. That slice is why the saving is 47 or 45 percent. Values alone would save exactly half.

Rebuilt keys started far smaller than queries and flattened attention

Rebuilt keys started far smaller than queries and flattened attention
The fix starts each map so key size matches query size
each panel has its own colour scale
the paper’s illustration · ten positions · not a training run
colour bar spans 0.0034 to 0.0046 · flat
up to 0.14
Tripathi, Kumar, Khan · FrontiersMind · “Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction” · arXiv 2609.13285 · Sep 2026

The rebuilt keys also started at the wrong size. With the usual starting values, the keys came out far smaller than the queries. Attention then spread almost evenly across every word, and early training spent its steps recovering. The team now starts each map so key size matches query size. Figure 4 is the paper's sketch of that effect, on ten made-up positions. Each panel has its own colour scale. The busy middle panel is the flat one, because its colour bar barely changes.

Grouped Value Attention scores 44.35 percent against GQA 44.36 percent

Grouped Value Attention scores 44.35 percent against GQA’s 44.36 percent
MLA 43.88 percent · the authors call it near-GQA quality
Table 2 · accuracy, percent HellaSwag WinoGrande OpenBookQA ARC-
Easy
ARC-
Challenge
Average
Grouped Value Attention, scale-matched 42.0553.5134.4062.7529.3544.41
GQA 43.4152.4833.4063.4229.0944.36
Grouped Value Attention, position slice 16 42.6953.3533.6063.8128.3244.35
Grouped Value Attention, position slice 24 42.9453.1233.2063.6928.5044.29
MLA 43.2051.6134.6062.8727.1343.88
about 350 million parameters · 30 billion FineWeb-Edu tokens · mean of three runs · zero-shot
0.01 points apart
44.41 · ordinary rotation · cannot fold
Tripathi, Kumar, Khan · FrontiersMind · “Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction” · arXiv 2609.13285 · Sep 2026

Every model here has about 350 million parameters. Each trained on 30 billion tokens of FineWeb-Edu, a public set of educational web pages. The team trained each design three times from different random starting points and averaged the scores. The quizzes run with no worked examples first. GQA averages 44.36 percent. Grouped Value Attention with the 16-number position slice averages 44.35 percent, and with the 24-number slice, 44.29 percent. MLA averages 43.88 percent. The top row in the table, at 44.41 percent, uses ordinary rotation, so that version cannot use the fold.

The 47 percent saving counts stored numbers and has no timing yet

The 47 percent saving counts stored numbers and has no timing yet
Kernels built and in testing · release planned
GQA
100
Grouped Value Attention
position slice 24
55
Grouped Value Attention
position slice 16
53
cached numbers per token, GQA = 100
built from the paper’s Eq. 13 and stated savings · a count, not measured memory
counted, not timed
arXiv listing summary 44.18   ·   paper, v1 and v2 44.35
speed · latency · peak memory · batch size: unmeasured one model size · one dataset · three runs context length unstated no spread across runs printed
Tripathi, Kumar, Khan · FrontiersMind · “Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction” · arXiv 2609.13285 · Sep 2026

The 45 to 47 percent saving counts stored numbers. The paper reports no decoding speed, latency, peak memory or batch size. The authors say they have built custom kernels, the low-level GPU code that would turn a smaller cache into faster serving. They are testing those kernels now, with a release planned. Every comparison uses one model size, one dataset and three runs. The paper does not state the context length and runs no long-context test. The arXiv listing's summary gives 44.18 percent for the headline version. Both versions of the paper say 44.35 percent. The model the team released is Lumma, a 0.6 billion-parameter base model. Lumma uses the first cut from Figure 3, where each value doubles as its key.

Skim it

Skim it
Skim it for the fold and the shared position key
Implement it after kernels and timings land at a larger scale
Section 3 · Equation 7 · the shared position key
Vishesh Tripathi · Abhay Kumar · Ramsha Khan
“Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction”
FrontiersMind · arXiv 2609.13285 · v2, 15 September 2026 · preprint
Figure 1 · Grouped Value Attention panel, already seen
Tripathi, Kumar, Khan · FrontiersMind · “Grouped Value Attention: Efficient KV Caching via On-Demand Key Reconstruction” · arXiv 2609.13285 · Sep 2026

Skim it. Read section 3 for the fold and the shared position key, if the KV cache limits the models you run or design. Hold off on implementing it. The evidence is one model size of about 350 million parameters, with zero timings, and the kernels are unreleased. The authors say the throughput numbers come with that kernel release. The paper is Grouped Value Attention, by Vishesh Tripathi, Abhay Kumar and Ramsha Khan at FrontiersMind. It is an arXiv preprint, number 2609.13285.