Repository navigation
Document ARAM residency opportunities across SDK, engine and AnimalTown - #20
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.