deb-murano/releasenotes/notes/gc-collect-165e73bbaf345d74.yaml
Stan Lagun 584571c3d8 On-demand garbage collection
Garbage collection is triggered by io.murano.system.GC.collect()
static method. Garbage collector destroys all object that are not
reachable anymore. GC can handle objects with cross-references and
isolated object graphs. When portion of object model becomes not
reachable it destroyed in predictable order such that child objects get
destroyed before their parents and, when possible, before objects
that are subscribed to their destruction notifications.

Internally, both pre-deployment garbage collection (that was done by
comparision of ``Objects`` and ``ObjectsCopy``) and post-deployment
orphan object collection are now done through the new GC.

MuranoPL GC utilizes Python GC to track and collect objects.
The main idea is to make ObjectStore have weak links only and
prevent hard links in other dsl places so that only links between objects
remain. Then prevent Python GC to automatically delete objects that
are not used anymore and use gc.collect() to obtain a list of
objects that are both not reachable and cannot be destroyed and then
destroy them in the correct order.

Targets-blueprint: dependency-driven-resource-deallocation
Closes-Bug: #1619635
Closes-Bug: #1597747
Change-Id: I653d8f71f003afa0a1ea588c9d14198571f5ad14
2016-09-14 03:43:09 +00:00

14 lines
782 B
YAML

---
features:
- New on-request garbage collector for MuranoPL objects were implemented.
Garbage collection is triggered by io.murano.system.GC.collect()
static method. Garbage collector destroys all object that are not
reachable anymore. GC can handle objects with cross-references and
isolated object graphs. When portion of object model becomes not
reachable it destroyed in predictable order such that child objects get
destroyed before their parents and, when possible, before objects
that are subscribed to their destruction notifications.
- Internally, both pre-deployment garbage collection (that was done by
comparision of ``Objects`` and ``ObjectsCopy``) and post-deployment
orphan object collection are now done through the new GC.