Skip to content

bench: cpu_bench harness (fork vs upstream)#87

Open
adubovikov wants to merge 2 commits into
duckdb:mainfrom
adubovikov:perf/upstream-pr/5-cpu-bench-harness
Open

bench: cpu_bench harness (fork vs upstream)#87
adubovikov wants to merge 2 commits into
duckdb:mainfrom
adubovikov:perf/upstream-pr/5-cpu-bench-harness

Conversation

@adubovikov
Copy link
Copy Markdown
Contributor

Summary

Adds the cpu_bench/ tree: compare + workload modules to reproduce process-level and per-scenario CPU/CGO/heap deltas between the published module and a local replace build (see cpu_bench/README.md).

Optional / after the perf binding PRs (#83 series). Diff vs main includes the full binding series until those merge; can rebase this branch onto upstream/main once perf PRs land, or merge as a separate follow-up.

Standalone cpu_bench/compare and cpu_bench/workload modules to
reproduce process-level and per-scenario CPU/CGO deltas.
@adubovikov adubovikov marked this pull request as ready for review May 18, 2026 09:12
@adubovikov adubovikov force-pushed the perf/upstream-pr/5-cpu-bench-harness branch from d00be2d to 4289550 Compare May 18, 2026 09:12
@adubovikov
Copy link
Copy Markdown
Contributor Author

Rebased onto current main (post-#83). Branch is now one commit on top of upstream/main: 4289550 (same cpu_bench/ tree as before, cherry-picked from d00be2d). No binding changes in this PR. go test ./... and cpu_bench/compare + cpu_bench/workload builds checked. Force-pushed perf/upstream-pr/5-cpu-bench-harness; draft cleared.

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