Static pruning is widely used to accelerate sparse neural retrieval, yet existing studies each validate their conclusions within a single custom pipeline, leaving it unclear which findings transfer to modern engines with different index organizations and dynamic pruning mechanisms. We present the first cross-engine pruning portability study, evaluating static pruning strategies across three engines - a controlled C++ pipeline (exhaustive inverted index), BMP (block-max pruning), and SEISMIC (clustered inverted indexes) - on two benchmarks (MS MARCO, Natural Questions) with two encoders spanning opposite query-density regimes (SPLADE: 44 avg. query terms; V3-GTE: 7 avg. query terms), totaling 1,140 experimental configurations, with an additional deep-judgment validation on TREC DL 2019/2020. We find that index-side pruning (document and posting-list) is portable: it consistently reduces latency (1.2-6.6×) and index size (18-82%) across all engines because sparse retrieval is memory-bound - a conclusion we support with cache-miss, TLB, and IPC profiling. In contrast, query pruning is already internalized by modern engines: it yields 4-11× speedup on the exhaustive pipeline but is subsumed by BMP's β and SEISMIC's query_cut. Static pruning complements dynamic pruning: on BMP, combining document and query reduction yields 2.5× speedup with NDCG@10 within 0.003 of the exact baseline. Finally, NDCG@10 saturates while Recall@10 is still in the ∼85-95% range across all three engines, providing a portable stopping criterion: practitioners can push pruning to this knee without visible ranking degradation. Together, these findings answer what transfers (index-side pruning), what breaks (query pruning), and what still helps (static atop dynamic pruning).
Figures & tables
Configuration
Query nnz
Doc nnz
Docs
NDCG@10
DL’19/20
MS MARCO + SPLADE
43.95
119.96
8.8M
0.449
0.726
MS MARCO + V3-GTE
6.89
180.41
8.8M
0.428
0.720
NQ + SPLADE
46.97
147.52
2.7M
0.539
—
NQ + V3-GTE
7.20
185.00
2.7M
0.582
—
Table 1. Dataset and encoder statistics. Avg. non-zero counts (nnz) per query and document, corpus size, baseline NDCG@10 on the controlled pipeline, and baseline NDCG@10 on the deep-judgment TREC DL 2019/2020 topics (mean over both years; MS MARCO corpus).
Figure 1. Custom C++ Pareto frontiers on MS MARCO: speedup vs. Recall@10 for all six pruning families ({Doc, Query, Posting} × {Alpha-Mass, Max-Ratio}). Left : SPLADE. Right : V3-GTE. Document pruning provides the most stable high-recall frontier across both encoders. Six Pareto curves comparing pruning families on two encoder regimes. Document pruning provides the most stable frontier in both.
Dataset+Enc.
Pruning
Lat. (ms)
Spd.
Idx (GB)
R@10
NDCG
MRR
MS+SPL
Baseline
70.1
1.0 ×
8.15
1.000
0.449
0.383
Q AM 0.50
11.5
6.1 ×
8.15
0.964
0.448
0.383
Doc AM 0.50
11.7
6.0 ×
1.53
0.928
0.443
0.379
Doc MR 0.30
18.1
3.9 ×
2.16
0.974
0.447
0.381
Post MR 0.30
15.6
4.5 ×
2.00
0.979
0.447
0.382
MS+GTE
Baseline
29.5
1.0 ×
12.23
1.000
0.428
0.362
Table 2. Controlled pipeline ( Ψ ): representative operating points with two-stage re-rank ( k′ = 50). Speedup relative to unpruned baseline. Idx is the in-memory inverted-index size.
Figure 2. SEISMIC Pareto frontiers (qc = 5): speedup vs. Recall@10 under document and query pruning for both encoders. Document pruning provides consistent gains; query pruning overlaps with SEISMIC’s internal query_cut . SEISMIC Pareto curves showing document pruning provides consistent gains while query pruning overlaps with internal query cut.
Speedup
Recall@10
Δ NDCG@10
Δ MRR@10
Config
Pruning
C++
C++ †
BMP
SEIS.
C++
C++ †
BMP
SEIS.
C++
C++ †
BMP
SEIS.
C++
C++ †
BMP
SEIS.
MS+SPL
Doc AM 0.90
1.49 ×
1.48 ×
1.43 ×
1.18 ×
1.000
.946
.948
.868
.000
− .003
− .003
− .005
.000
− .003
− .002
− .005
Post MR 0.10
1.56 ×
1.54 ×
1.47 ×
1.17 ×
1.000
.947
.948
.871
.000
− .002
− .001
− .004
.000
− .002
− .002
− .004
Query MR 0.10
1.68 ×
1.65 ×
1.91 × ∗
1.17 ×
1.000
.945
.935
.924
.000
.000
.000
+.001
.000
− .001
.000
.000
MS+GTE
Doc AM 0.90
1.78 ×
1.61 ×
1.23 ×
1.42 ×
1.000
.969
.969
.937
.000
− .001
− .001
− .002
.000
.000
− .001
− .001
Post MR 0.10
1.86 ×
1.68 ×
1.27 ×
1.58 ×
1.000
.970
.969
.939
.000
− .002
− .002
− .002
.000
− .001
− .002
− .002
Table 3. Portability Matrix: three pruning methods × four configurations, each evaluated on three engines. Speedup is relative to each engine’s unpruned baseline. Δ NDCG and Δ MRR show absolute change vs. the exact baseline (negative = degradation); Δ MRR tracks Δ NDCG throughout. C++ uses two-stage re-ranking ( k′ = 50); C++ † shows single-stage (no re-ranking) for direct comparison with BMP/SEISMIC. ∗ BMP external query MR at β = 1.0.
Figure 3. Per-query latency histogram strips on MS MARCO+SPLADE (controlled pipeline) at four document-pruning levels. The P50/P90/P95 markers show progressive IQR compression: moderate pruning ( αd = 0.9) narrows the distribution while aggressive pruning ( αd = 0.5) concentrates it tightly with minimal tail degradation. Histogram strips showing per-query latency distributions at four pruning levels with KDE outlines and percentile markers.
Index
Query
Lat. ( μ s)
Spd.
R@10
NDCG
MRR
Idx
Full
Full
8,915
1.00 ×
1.000
0.449
0.382
15.7
Full
Q MR 0.10
4,680
1.91 ×
0.935
0.449
0.382
15.7
Pruned
Full
6,235
1.43 ×
0.948
0.446
0.380
10.1
Pruned
Q MR 0.10
3,537
2.52 ×
0.917
0.446
0.379
10.1
Table 4. BMP 2 × 2 factorial on MS MARCO+SPLADE ( α = 1.0). Speedup relative to the full-index, full-query baseline. Index size in GB.
Figure 4. BMP 2 × 2 factorial on MS MARCO+SPLADE: latency under four conditions (full/pruned index × full/pruned queries). Recall@10 shown inside each bar. Combined pruning achieves the largest speedup (2.52 × ) with minimal NDCG loss ( Δ NDCG = − 0.003). Bar chart showing four BMP conditions with latency bars and recall values. Combined pruning achieves the best speedup.
Index
Query
Lat. ( μ s)
Spd.
R@10
NDCG
MRR
Idx
Full
Full
185
1.00 ×
0.977
0.443
0.379
8.1
Full
Q MR 0.10
161
1.15 ×
0.924
0.444
0.379
8.1
Pruned
Full
158
1.17 ×
0.868
0.438
0.374
6.0
Pruned
Q MR 0.10
133
1.39 ×
0.856
0.440
0.376
6.0
Table 5. SEISMIC on MS MARCO+SPLADE (qc = 5, hf = 1.0). Speedup relative to the unpruned baseline at qc = 5. Index size in GB.
Figure 5. Micro-architectural profiling of Φ / Ψ / Ξ with Linux perf on multiple pruning configurations: (a) cache-miss rate, (b) IPC, (c) dTLB-miss rate, (d) per-query latency vs. cache-miss rate ( R2 = 0.84). Latency is tightly coupled to memory locality, not arithmetic throughput. Four-panel profiling figure: bar charts for cache-miss rate, IPC, and dTLB-miss rate, plus a scatter plot of latency versus cache-miss rate with regression line.
Engine
Config
IPC
Cache%
dTLB%
CacheMiss/Q
C++ Φ
scatter-add
1.58
30.0
97.0
740,000
C++ Ψ
window-switch
2.50
2.7
2.6
67,000
BMP
β =1.0
3.37
1.3
28.4
114,000
BMP
β =0.5
3.37
1.8
25.0
89,000
SEISMIC
qc=20
3.01
10.9
40.9
12,500
SEISMIC
qc=5
3.29
7.7
37.7
6,500
Table 6. Micro-architectural profile across engines (MS MARCO+SPLADE). Cache-miss and dTLB-miss are rates; CacheMiss/Q is the absolute count per query driving latency.
Figure 6. Latency vs. quality across three engines (columns) and two dataset–encoder regimes (rows: MS MARCO+SPLADE, top; NQ+V3-GTE, bottom). The dashed line marks the NDCG@10 knee (the most aggressive point within 0.005 of the unpruned baseline); the gold-shaded region to its right is where NDCG@10 has saturated while Recall@10 keeps rising, confirming the metric gap is engine-independent. Six panels: three engines (columns) by two dataset–encoder regimes (rows). A dashed line marks the NDCG knee in each panel; the gold-shaded region to its right highlights where NDCG has saturated while Recall keeps rising.
Appendix figures & tables4 assets
Supplementary material from the paper’s appendix.
Appendix
Config
Pruning
Idx (GB)
Lat ( μ s)
R@10
NDCG
MRR
Spdup
MS+SPL
None
15.7
8,915
1.000
0.449
0.382
1.00 ×
AM 0.50
4.3
2,869
0.685
0.398
0.335
3.11 ×
AM 0.70
6.4
4,166
0.832
0.431
0.366
2.14 ×
AM 0.90
10.1
6,235
0.948
0.446
0.380
1.43 ×
AM 0.95
11.7
7,111
0.972
0.448
0.381
1.25 ×
MR 0.10
10.4
6,281
0.951
0.446
0.380
1.42 ×
Appendix
Table 7. BMP document/posting/query pruning across all four dataset–encoder combinations ( α =1.0). Speedup relative to each config’s unpruned baseline.
Figure 7. Recall@10 under document pruning across the four dataset–encoder combinations. The two-stage C++ curve shows the effect of full-vector re-ranking, while the no-rerank C++ curve closely tracks BMP at the main operating point (AM=0.90). SEISMIC exhibits a larger Recall drop under the same static pruning threshold, indicating that pruning thresholds have different effective severity under cluster-based traversal. The gray band marks Recall@10 ≥0.90 . Four-panel figure comparing Recall@10 under document alpha-mass pruning for C++ with reranking, C++ without reranking, BMP, and SEISMIC.
Config
Pruning
Idx (GB)
Lat ( μ s)
R@10
NDCG
MRR
MS+SPL
None
8.1
186
0.977
0.443
0.379
AM 0.70
4.3
140
0.769
0.424
0.361
AM 0.90
6.0
158
0.868
0.438
0.374
AM 0.95
6.7
167
0.889
0.441
0.378
NQ+SPL
None
7.0
234
0.937
0.533
0.485
AM 0.70
4.5
167
0.727
0.505
0.460
Appendix
Table 8. SEISMIC document pruning across all configurations (qc=5, hf=1.0).
Ningbo Institute of Digital Twin, Eastern Institute of Technology, Ningbo · Department of Computing, The Hong Kong Polytechnic University · Munich Center for Machine Learning, LMU Munich