Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
keeping completed plans in unarchived state causes memory pressure #79
Our system model is huge and there are various copies of SystemModel and associated SystemEntries (some that are made for filtering for ex.). Another area is ProgressTracker holds on to SystemModel -- ProgressTrackers inturn is held by Deployments which are not archived yet. This causes memory bloat at worse, and huge GC times when the plans are archived (and those references released) at best.
A solution might be to constantly archive old plans -- based on how old they are. User configurable cutoff period with a default of 30mins would be nice.
We implemented something like in our PlanController, but a nicer solution with an archival thread would be useful for the community.