Skip to content

Document ARAM residency opportunities across SDK, engine and AnimalTown - #20

Merged
capz merged 2 commits into
mainfrom
docs/aram-residency-audit
Nov 13, 2026
Merged

capz merged 2 commits into
mainfrom
docs/aram-residency-audit

Conversation

@capz

@capz capz commented Nov 12, 2026

Copy link
Copy Markdown
Owner

Existing ARAM APIs do not by themselves reclaim MEM1 safely during gameplay. This investigation traces current DolphinDotNet, Hypercube and AnimalTown ownership and transfer paths, then ranks residency opportunities and the work needed to preserve frame time.

The strongest first candidate is AnimalTown's 1 MiB outdoor MEM1 cache while indoors: its immutable backing is already in ARAM. Cold shared species models offer larger conditional savings; the report includes SHA-verified historical asset sizes and explicitly distinguishes them from current-build measurements. It also identifies the shared DMA contention failure in AnimalTown terrain, unbounded SDK model restore/retirement work, and Hypercube's distinction between source caching and actual resident-memory release.

Includes pinned source citations, current consumer-version differences, global ARAM budgets, machine-readable inventories, implementation priorities and matched hardware-performance acceptance criteria. Runtime paging is not enabled by this documentation change.

Validation: existing focused SDK native ARAM allocation/fragmentation/lifetime/fault test passed; budget and asset arithmetic checked; all 13 pinned source citations and local JSON links verified; docs-only CI selection and whitespace checks passed. No console build was needed, and no new hardware performance claim is made.

@capz
capz merged commit 3a322e6 into main Nov 13, 2026
12 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