add clickhouse-backed oteldb variant + --only fast-loop mode#1
Merged
Conversation
oteldb-ch: same binary without --embedded, serving all three query APIs from chstorage on a dedicated clickhouse-oteldb server (isolated footprint). Wired into the ingest fan-out (vmagent remote-write, otelcol logs+traces) and systems.yml with a per-system volume override for footprint accounting. --only <csv> (or BENCH_ONLY): restrict a run to a subset of engines, bringing up just those plus the lane's ingest driver and querying/collecting/reporting only them — a fast feedback loop (e.g. --only oteldb,oteldb-ch for a head-to- head of the embedded vs ClickHouse storage).
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
1 participant
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.
oteldb-ch: same binary without --embedded, serving all three query APIs from chstorage on a dedicated clickhouse-oteldb server (isolated footprint). Wired into the ingest fan-out (vmagent remote-write, otelcol logs+traces) and systems.yml with a per-system volume override for footprint accounting.
--only (or BENCH_ONLY): restrict a run to a subset of engines, bringing up just those plus the lane's ingest driver and querying/collecting/reporting only them — a fast feedback loop (e.g. --only oteldb,oteldb-ch for a head-to- head of the embedded vs ClickHouse storage).