BigMemory Max 4.3.3 | Product Documentation | BigMemory Max Administrator Guide | Terracotta Configuration Parameters | The Servers Parameters | /tc:tc-config/servers/garbage-collection
 
/tc:tc-config/servers/garbage-collection
This section lets you configure the periodic distributed garbage collector (DGC) that runs in the TSA. The DGC collects shared data made garbage by Java garbage collection.
For many use cases, there is no need to enable periodic DGC. For caches, the more efficient automatic inline DGC is normally sufficient for clearing garbage. In addition, certain read-heavy applications will never require the periodic DGC as little shared data becomes garbage.
However, concerning certain data structures, the periodic DGC may need to be enabled. Inline DGC may not be available for all data structures.
For more on how DGC functions, see Managing Distributed Garbage Collection.
Here is a configuration snippet:
<garbage-collection>
<!-- Default: false -->
<enabled>true</enabled>

<!-- If "true", additional information is logged when a
server performs distributed garbage collection.

Default: false
-->
<verbose>false</verbose>

<!-- How often should distributed garbage collection
be performed, in seconds?

Default: 3600 (60 minutes)
-->
<interval>3600</interval>
</garbage-collection>
Copyright © 2010 - 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.