DuckDB CPU attribution: dedicated executor + KurrentDB integration#5655

Draft

realtonyyoung wants to merge 17 commits into

spec/duckdb-cpu-attribution

Commits on Jun 27, 2026

Add design spec: DuckDB CPU attribution via dedicated executor

realtonyyoung
and
claude
committed

Commits on Jul 1, 2026

Address spec review: #5642 wording, dashboard formula, typo

realtonyyoung
and
claude
committed

Commits on Jul 2, 2026

Add implementation plan: DuckDB executor integration + /metrics wiring

realtonyyoung
and
claude
committed
docs(plan): note arm64 local build must not use /p:Platform=x64

realtonyyoung
and
claude
committed
chore: consume Kurrent.Quack executor build (local feed placeholder version)

realtonyyoung
and
claude
committed
feat: DuckDB executor lifetime owns DB open; remove per-connection pool plumbing

realtonyyoung
and
claude
committed
feat: kurrentdb.duckdb.cpu.seconds observable counter over executor CPU samples

realtonyyoung
and
claude
committed
feat: index processors run DuckDB work on executor dispatchers (pinned connections)

realtonyyoung
and
claude
committed
feat: index readers execute on DuckDB dispatchers

realtonyyoung
and
claude
committed
feat: QueryEngine and stats run on DuckDB dispatchers; Quack owns query cancellation

realtonyyoung
and
claude
committed
test: fixtures build on DuckDB executor

realtonyyoung
and
claude
committed
fix: bridge SchemaRegistry's DuckDBConnectionPool to the executor's shared DB

realtonyyoung
and
claude
committed
docs: correct UiStatsService class comment (dispatcher, not thread-pool offload)

realtonyyoung
and
claude
committed
fix: address final whole-branch review findings

realtonyyoung
and
claude
committed

Commits on Jul 3, 2026