Requirements for using DGC
There are two applications for DGC: SstDistributedGC and SstDistributedGCCoordination. Both applications must be loaded in the DGC Coordinator's image. All other images need only load SstDistributedGC.
There are some additional requirements which must be met before DGC can be used in a particular system.
The passing of objects as references must be supported. A by-value system has no requirement for DGC as no remote references are created.
The local spaces should be configured to support proxy finalization. This prevents object spaces from hanging on to imported remote references even though they are not used locally. This option is controlled by the space's configuration. Use either SstSpaceConfiguration finalizedProxyConfiguration or SstSpaceConfiguration finalizedProxyConfiguration. These must be specified before the configured object space is started.
The key used for manually exported objects (for example, using export:as:) must answer true to sstIsTransientKey if the exported object is to participate in DGC. By default, only SmallIntegers are transient keys. Objects exported using Symbols, for example, are not subject to DGC.
Last modified date: 01/29/2015