Skip to content

Bound the EOS table caches that grow with every regeneration #821

Description

@timlichtenberg

The module-level EOS table caches in src/proteus/interior_energetics/aragog.py (_entropy_eos_cache and _entropy_eos_jax_cache) grow without bound. Each table regeneration produces a new content key, and each miss adds a permanent entry holding a full interpolator set (and JAX artifacts on that path) for a table set that will never be read again, since regenerated tables never revert to an old content key.

On a long accretion run with #817, every impact regenerates the tables, and composition-triggered regenerations add more entries. Keep-last-N eviction (N=2 is enough for any rollback the solver can perform) would bound memory with no behaviour change.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    InterraIssue has been imported to the Interra Board projectimport

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions