New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keeping completed plans in unarchived state causes memory pressure #79

Closed
li-mdubey opened this Issue Jul 19, 2011 · 0 comments

Comments

Projects
None yet
2 participants
@li-mdubey
Contributor

li-mdubey commented Jul 19, 2011

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.

@ghost ghost assigned ypujante Sep 13, 2011

ypujante added a commit that referenced this issue Sep 16, 2011

#79: list of archived does not fetch details
somewhat related to issue #79 (for archive tab)

ypujante added a commit that referenced this issue Sep 16, 2011

ypujante added a commit that referenced this issue Sep 16, 2011

#79: automatically archive 'old' plans
 - configurable via console.deploymentService.autoArchiveTimeout property (default to 30m)

@ypujante ypujante closed this Sep 16, 2011

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