Skip to content

feat(bench): add AggOp memory profiler#144

Open
tristanle22 wants to merge 9 commits into
beava-dev:mainfrom
tristanle22:aggop-memory-profiler
Open

feat(bench): add AggOp memory profiler#144
tristanle22 wants to merge 9 commits into
beava-dev:mainfrom
tristanle22:aggop-memory-profiler

Conversation

@tristanle22
Copy link
Copy Markdown

@tristanle22 tristanle22 commented May 15, 2026

Summary

Adds a memprofile bench binary for profiling per-AggOp structural memory usage against the workloads. This is the first part of #68, which enables further analysis.

Linked issues

Related to #68


What changed

This PR adds a memprofile bench binary that profiles structural memory usage for each AggOp in the fraud workload. It introduces reusable MemUsage / MemProfile accounting in beava-core, generates a ranked Markdown report of per-op stack and heap estimates, and highlights the largest memory contributors.

Verification

Paste the summary block from bash .github/scripts/check.sh here so the
reviewer can see the local run passed:

PASS  cargo fmt --all --check  (0s)
PASS  cargo clippy --workspace --all-targets --features testing -- -D warnings  (1s)
PASS  cargo test --workspace --features testing  (22s)
PASS  ruff check python/  (0s)
PASS  mypy --strict beava/
PASS  pytest python (v0 acceptance suite)  (16s)

Pre-flight checklist

  • bash .github/scripts/check.sh exits 0 (or each step passes manually)
  • Verification block above replaced with real output
  • Docs updated (docs/*.md, beava-website/project/docs/, decorator docstrings) if user-visible behavior changed
  • No stale repository URLs (canonical: beava-dev/beava)
  • If this commits a schema change to beava-website/deploy/site-metrics-pipeline.json, called out in this PR body — the deploy workflow re-registers with force=true, which silently lands destructive edits

@tristanle22 tristanle22 requested a review from petrpan26 as a code owner May 15, 2026 01:08
@tristanle22 tristanle22 marked this pull request as draft May 15, 2026 01:27
@tristanle22 tristanle22 marked this pull request as ready for review May 25, 2026 00:56
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