rust/greptimedb
1
0
Fork 0
mirror of https://github.com/GreptimeTeam/greptimedb.git synced 2026-10-13 07:22:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

test(perf): qualify millisecond range manipulation path

Browse Source 
Signed-off-by: discord9 <55937128+discord9@users.noreply.github.com>
This commit is contained in:
discord9
2026-09-29 15:47:44 +08:00
parent 20d87cff48
commit 067b73f605
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/perf/query_cases/promql_constant_tag_concat_ms/case.toml
+17
View File
@@ -58,6 +58,23 @@ step_nanos = 15_000_000_000
time_range_layout = "non_overlapping_per_sst"
series_layout = "timestamp_major"
# Range-vector qualification for the #9274 millisecond fast path: only the
# matrix selector `count_over_time(...[5m])` reaches RangeManipulateStream on
# this TIMESTAMP(3) fixture with zero offset, so ANALYZE VERBOSE is used to keep
# `PromRangeManipulateExec` in each measured sample. The instant selectors below
# remain the negative control (they never enter RangeManipulateStream). As the
# first configured query, this entry is also the runner's extra untimed
# pre-measurement validation probe.
[[scenario.queries]]
name = "range_count_over_time_5m_analyze"
kind = "tql"
query = "TQL ANALYZE VERBOSE (1704069000, 1704069900, '15s') count_over_time(promql_constant_tag_concat_ms[5m])"
warmup = 3
iterations = 9
[scenario.queries.thresholds]
max_candidate_latency_regression_pct = 10
[[scenario.queries]]
name = "selector_full"
kind = "tql"