From 587b72cc51f59d9144c8aadccd06818e064d839c Mon Sep 17 00:00:00 2001 From: Bradley Dice Date: Sun, 11 Oct 2026 23:27:54 +0000 Subject: [PATCH] Use itopk_size=128 in the core CAGRA multi-partition test sweep --- cpp/tests/neighbors/ann_cagra.cuh | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/cpp/tests/neighbors/ann_cagra.cuh b/cpp/tests/neighbors/ann_cagra.cuh index a662c32f03..4be2c8797c 100644 --- a/cpp/tests/neighbors/ann_cagra.cuh +++ b/cpp/tests/neighbors/ann_cagra.cuh @@ -2485,15 +2485,15 @@ inline std::vector generate_mp_inputs() split, graph_build_algo::NN_DESCENT, algo, - /*itopk_size*/ 64, + // With a single 10000-row partition, itopk_size=64 leaves + // the recall of the fp16/int8/uint8 datasets at ~0.98, with + // a tail below 0.97 since the NN-descent graph differs from + // build to build. 128 puts every case near 1.0 (minimum + // ~0.994 over thousands of builds), so the single-index + // 0.985 convention applies. + /*itopk_size*/ 128, metric, - // Lower than the single-index 0.985 convention. These - // low-redundancy single-partition / skewed configs dip - // further under filtering, where removing rows thins the - // survivors' graph connectivity; observed recall floors - // around 0.974, so 0.97 leaves headroom for run-to-run - // jitter while still catching real regressions. - /*min_recall*/ 0.97}); + /*min_recall*/ 0.985}); } } }