Conversation
This was referenced Sep 22, 2026
zzylol
force-pushed
the
perf/issue-758
branch
from
September 24, 2026 12:55
4530670 to
999cafd
Compare
zzylol
force-pushed
the
732-test-add-prometheus-remote-write-promql-differential-suite
branch
from
September 24, 2026 12:56
9c84758 to
00195cb
Compare
zzylol
changed the base branch from
732-test-add-prometheus-remote-write-promql-differential-suite
to
refactor/query-plan-dag-execution
September 24, 2026 12:57
zzylol
force-pushed
the
refactor/query-plan-dag-execution
branch
from
September 26, 2026 04:42
90154af to
6a9dc9c
Compare
zzylol
force-pushed
the
perf/issue-758
branch
from
September 26, 2026 04:42
b093ec3 to
4f284d0
Compare
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.
Problem and behavior
Before this PR: runtime/thread controls and a reproducible comparison of direct computation, installed-plan execution and HTTP overhead were missing.
After this PR: runtime controls and an inspection executable compare four paths over identical deterministic inputs: direct sketch, raw exact, backend bound-query execution and HTTP. Results must agree before measurements count as successful. Reports retain latency, throughput, request failures/drops, CPU, memory, threads, effective controls and cgroup limits.
Each cell now includes
installed-plan.json, six separately measured setup stages, and an explicit list of included/excluded architecture stages. Setup time is separate from request latency. The fixture installs imported state: it does not benchmark Planner search/physical compilation, backend deployment compilation, precompute execution or durable recovery. Listed request stages are not individually timed. Seedocs/developer_docs/performance/overhead-inspection.md.The inspection guide also explains how to retain the selected query-time or precomputed Rate/Sum/heap placement, including window width and stride. Runtime controls do not change those Planner decisions.
Stack
Based on #761. #766 and #756 are independent follow-ups; the acceptance stack does not depend on either. This PR does not require diagnostic logging to benchmark the production query path.
Validation and limits
Refs #758.