Repository navigation
phase 3: VictoriaMetrics vs ASAPQuery-backend on the five use cases - #245
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…Write and ask its queries at each evaluation time Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… planned to keep no raw samples Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…oard Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nt plan below its root Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…its costs; failed evaluations have no latency Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s each inside a path; wider columns Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…shboards as on main Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Phase 3 runs phase 2's five use cases, queries and data on two time series systems:
raw_data_retained: false, with its data plane started with--no-forward, so it keeps sketches only.Both systems get the same samples and the same instant queries, and are scored with phase 2's rules.
aqpbm-systemeval(new crate, binarysystemeval):/internal/force_flush.--speed Ntimes the data's own rate.planeval: answer scoring has moved toscore.rsso thatsystemevalcan share it.scripts/run_use_case_on_systems.py: one run covers one use case, every arm that keeps no raw samples, and both systems. Per arm it:control_plane, and marks the queries it cannot plan as not supported by ASAPQuery-backend;entropy_over_time), the in-process exact plan stands in.phase3/runs/under the served data directory.target/grafana-data/phase3by default.Results (noraw, max error 0.05, bulk)
distinct_5s,packets_5s;entropy_10sunless guarantees are ignoredtop10_clients_1m; on CAIDA and MAWI both top-k queries hit the executor memory limitKnown limits
05fb36e, older than planeval'sb822553. At05fb36e, a query whose window equals its interval cannot be planned without raw data.boundandrerunpolicies from phase 2 have not been carried over.Test plan
cargo build --releaseandcargo test --release --workspacepython3 -m unittest discover -p "test_*.py"inscripts/(233 tests)🤖 Generated with Claude Code