Skip to content

otel benchmark harness - #9

Merged
lmangani merged 3 commits into
mainfrom
chore/otel-benchmark-harness
Jul 31, 2026
Merged

otel benchmark harness#9
lmangani merged 3 commits into
mainfrom
chore/otel-benchmark-harness

Conversation

@lmangani

Copy link
Copy Markdown
Contributor

No description provided.

lmangani added 3 commits July 31, 2026 10:25
Bash + Python session driver with host-side timing, cold-then-warm in one
DuckDB process, warm schema-stability gate, and a main-level 100k baseline.
…f a fixed low cap.

AUTO_POOL_THREAD_CAP=4 and AUTO_PIPELINE_THREAD_CAP=8 clamped the
append-pool and parse-pipeline auto-scaling below the box's own
hardware_concurrency()/2 and *2/3 formulas, leaving cores idle on
many-core machines. Reusing the existing MAX_POOL_THREADS/
MAX_PIPELINE_THREADS=16 ceiling lets defaults scale with the machine;
verified with the full sqllogictest suite (663 assertions) and
back-to-back A/B ingest runs showing ~20-30% higher cold-ingest
throughput on a 20-core box with no regressions.
Re-measured ingest and query benchmarks on DuckDB v1.5.5 with the
scaled thread defaults: 1.35M/1.26M/970k records/s for traces/logs/
metrics (3M records in 2.6s), and 27-63x query speedup with 6x
smaller storage vs the JSON baseline.
@lmangani
lmangani merged commit f8f20a0 into main Jul 31, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant