perf(index): bypass range-result cache in targeted CI case

Signed-off-by: discord9 <55937128+discord9@users.noreply.github.com>

src/cmd/src/bin/query_regression_runner/remote/ingest.rs

@@ -34,7 +34,7 @@ pub(super) async fn run_render_remote_config(args: RenderRemoteConfigArgs) -> Re
     let config = match args.target {
         RemoteConfigTarget::Frontend => frontend_prom_config(&remote.prom_store)?,
         RemoteConfigTarget::Datanode if remote.disable_index_result_cache => {
-            "[[region_engine]]\n[region_engine.mito.index]\nresult_cache_size = \"0B\"\n"
+            "[[region_engine]]\n[region_engine.mito]\nrange_result_cache_size = \"0B\"\n[region_engine.mito.index]\nresult_cache_size = \"0B\"\n"
                 .to_string()
         }
         RemoteConfigTarget::Datanode => String::new(),

tests/perf/README.md

@@ -193,7 +193,7 @@ before trusting the query measurements. Use
 `--fixture-generator /path/to/query_perf_fixture` to provide the Rust helper to
 the outer driver.
 
-Remote-write cases can set `disable_index_result_cache = true` under `[scenario.remote_write]` to launch both base and candidate datanodes with Mito's index result cache set to `0B`; this keeps warmed query samples exercising the inverted/Bloom index applier rather than reusing cached index results. The default is false, so other cases are unchanged.
+Remote-write cases can set `disable_index_result_cache = true` under `[scenario.remote_write]` to launch both base and candidate datanodes with Mito's range result cache and index result cache set to `0B`; this avoids range/index result cache hits that bypass the applier; inspect actual EXPLAIN applier metrics to verify the query path. The default is false, so other cases are unchanged.
 
 Large manual remote-write cases can set `sample_chunk_size` to split ingestion by
 time. For each chunk, `prepare-remote` invokes `query_perf_fixture prom-remote-write` with the