Training-free sparse attention

SparsePR

Partition the Support. Reconstruct the Residual.

Training-Free Sparse Attention for
Video Generation and World Models

Pardis Taghavi · Reza Langari · Gaurav Pandey

Texas A&M University

TL;DRSparsePR couples executable response-aware partitions with a small set of exact probe rows to recover the residual that sparse attention leaves behind.
21.9–26.0%executed-pair density
1.48–2.61×end-to-end speedup
4models
0training steps

02 / Abstract

Executable sparsity needs more than concentrated attention.

Training-free block-sparse attention can accelerate video transformers, but attention concentration alone does not define an executable sparse operator. Shared query routes can expand support, and retained attention mass does not predict the output error from skipped interactions.

SparsePR combines Response-Coupled Partitioning with Probe-Fitted Residual Reconstruction. It groups queries and paired K/V tokens by current-call responses, then uses a small set of exact query rows to correct the sparse output. Across four models, SparsePR preserves quality at 22% to 26% executed-pair density with 1.48× to 2.61× end-to-end speedups.

03 / Why partition geometry matters

Why per-query sparsity is not executable sparsity.

Support density is the percentage of key tokens needed to retain 90% of attention mass. The pooled diagnostic measures their union across queries before block routing.

1 query · 6.2%8 queries · 22.9%
Single query

Per-query support

6.2%

One query needs a small key support.

Q1
Shared route

8 queries pooled

22.9%

Each query is sparse; a shared route must cover their union.

Q1
Q2
Q3
Q4
Q5
Q6
Q7
Q8
Route
Omitted key supportRetained key supportPooled support
Per-query sparsity versus pooled support density and normalized output error versus retained attention mass across four models
Per-query concentration does not determine pooled support, and retained attention mass does not determine output error.

04 / Method

One response geometry.
Two coupled stages.

SparsePR constructs the executable partition and reconstructs its error using features from the same current attention call.

01Sample responses

Probe a compact subset of queries against K/V.

02Partition support

Form paired K/V groups, then response-aligned query groups.

03Execute sparse routes

Select and evaluate hardware-ready query–K/V cells.

04Reconstruct residual

Fit a call-specific correction from exact probe rows.

RCP

Response-Coupled Partitioning

Sampled query responses define value-aware paired K/V groups. Their centroids become query-response coordinates, aligning queries that can efficiently share one route.

PFRR

Probe-Fitted Residual Reconstruction

A small stratified set of query rows is evaluated exactly. Their observed post-softmax residuals fit an affine correction in a low-rank probe-residual subspace.

05 / Results

Quality and efficiency across four video models.

All quantitative results from the final draft. Values use matched hardware and sequence shapes where reproduced. Density includes routing and exact probe pairs.

Table 1

Quality and efficiency

Reference fidelity, task quality, executed-pair density, attention PFLOPs, and end-to-end speedup.
ModelMethodPSNR ↑SSIM ↑LPIPS ↓ImgQual ↑SubCons ↑PBench ↑Density ↓PFLOPs ↓E2E ↑
HunyuanVideo-13BDense0.8500.976100%612.381.00×
HunyuanVideo-13BSpargeAttn†24.5890.7960.2320.90840.09%389.761.38×
HunyuanVideo-13BSVG2†30.4520.9100.1170.8520.92725.45%299.022.30×
HunyuanVideo-13BSVOO†24.8790.8430.2240.67930.97992.17×
HunyuanVideo-13BSVG-EAR†31.0430.9280.0920.8450.90322.17%281.861.93×
HunyuanVideo-13BSparsePR31.8440.9320.0870.8500.97621.92%255.952.61×
Wan2.2-I2V-A14BDense0.6890.974100%658.461.00×
Wan2.2-I2V-A14BSpargeAttn†27.1400.8830.1160.6800.95830.15%396.831.58×
Wan2.2-I2V-A14BSVG2†26.5620.8610.1380.6680.95931.28%393.951.59×
Wan2.2-I2V-A14BSVOO†29.6780.9130.0950.73370.97311.61×
Wan2.2-I2V-A14BSVG-EAR†29.7590.9180.0930.6800.95923.64%378.881.61×
Wan2.2-I2V-A14BSparsePR30.6580.9070.0440.6870.97321.97%328.701.80×
Cosmos-Predict2.5-14BDense0.7140.97677.76100%526.871.00×
Cosmos-Predict2.5-14BSVG220.0750.6240.3300.6780.89676.1428.81%286.511.24×
Cosmos-Predict2.5-14BSVOO22.0660.6850.2890.7010.90976.0337.63%315.381.03×
Cosmos-Predict2.5-14BSVG-EAR25.5490.9080.0620.7100.97677.7829.75%289.691.10×
Cosmos-Predict2.5-14BSparsePR26.3280.9420.0680.7140.97677.7522.14%253.611.51×
Cosmos3-Nano-16BDense0.7000.95077.31100.00%90.011.00×
Cosmos3-Nano-16BSVG222.4580.7350.2160.6770.91575.0337.29%57.691.16×
Cosmos3-Nano-16BSVOO16.6420.5730.3810.7070.96277.5967.32%69.511.02×
Cosmos3-Nano-16BSVG-EAR21.1670.7090.2610.6580.87272.8537.18%57.641.10×
Cosmos3-Nano-16BSparsePR24.4170.8010.1760.6990.94977.3025.96%43.221.48×

† Reported by prior work. Rows without † are reproduced under matched hardware, sequence shape, and timing protocols.

Error reduction from response-coupled partitioning across four models and Wan2.2 full-generation latency breakdown
Response-coupled partitioning reduces mean and p99 error at 22% density. On Wan2.2, SparsePR reaches 1.80× speedup and probe repair uses 1.1% of total latency.

Table 2

Partitioning and reconstruction ablations

Mean / p99 normalized attention-output error at 22% total executed-pair density. Lower is better.
ConfigurationHunyuanVideoWan2.2Cosmos-Predict2.5Cosmos3-Nano
Semantic partition0.0887 / 0.71360.1634 / 1.73380.7903 / 7.53180.3590 / 3.3557
Key-response K/V partition0.0851 / 0.81210.1560 / 1.65910.7686 / 7.27000.3409 / 3.1738
Response-coupled partition0.0736 / 0.69670.1489 / 1.64790.7617 / 7.22710.3315 / 3.1502
Semantic + probe repair0.0527 / 0.35620.1041 / 0.81860.2622 / 0.82600.1720 / 0.8648
SparsePR0.0330 / 0.22850.0707 / 0.43050.0954 / 0.57690.0822 / 0.4951

06 / Citation

Build on SparsePR.

@article{sparsepr2026,
  title   = {Partition the Support, Reconstruct the Residual:
             Training-Free Sparse Attention for Video Generation and World Models},
  author  = {Taghavi, Pardis and Langari, Reza and Pandey, Gaurav},
  journal = {arXiv preprint arXiv:2608.18484},
  eprint  = {2608.18484},
  archivePrefix = {arXiv},
  year    = {2026}
}