Skip to content

Document memory requirements for US budgetary impact example#333

Open
vahid-ahmadi wants to merge 1 commit intomainfrom
note-us-budgetary-impact-memory
Open

Document memory requirements for US budgetary impact example#333
vahid-ahmadi wants to merge 1 commit intomainfrom
note-us-budgetary-impact-memory

Conversation

@vahid-ahmadi
Copy link
Copy Markdown

Refs #328

Summary

  • The US budgetary impact example holds two full enhanced-CPS simulations in memory simultaneously and has been observed to peak at ~7.5 GiB RSS / ~80 GiB virtual on a 2026 dataset, with ~20 minute end-to-end runtime.
  • This PR adds an interim system-requirements note to the example header so users (and JOSS reviewers) know what to expect before running.
  • The underlying memory footprint is upstream in policyengine-us and is tracked separately in examples/us_budgetary_impact.py consumes excessive memory (peak ~7.5 GB RSS / 82 GB VMS) #328 — this is documentation only.

Test plan

  • Read the updated docstring at the top of examples/us_budgetary_impact.py.

🤖 Generated with Claude Code

Refs #328

Adds a system-requirements note to the example header documenting the
peak memory and runtime observed on the enhanced CPS 2026 dataset, so
users know what to expect before running. This is interim documentation
while the underlying policyengine-us memory footprint is investigated.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vahid-ahmadi vahid-ahmadi requested a review from anth-volk May 6, 2026 11:07
@vahid-ahmadi vahid-ahmadi self-assigned this May 7, 2026
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