Bug 47797

GemStone/S 64 Bit

3.4.2, 3.4.1, 3.4, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3

3.4.3, 3.3.9

Reclaim configuration parameters revert to speed-optimized values

During reclaimAll or finalization after other garbage collection operations, some Reclaim GcGem configurations are set to values that optimize performance by using all system resources.  This is intentional; however, these are not being reset to the application-defined settings afterwards.

The following parameters are affected:
   #deadObjsReclaimedCommitThreshold
   #objsMovedPerCommitThreshold
   #sleepTimeBetweenReclaimMs
   #sleepTimeWithCrBacklogMs
   #reclaimDeadEnabled

As of v3.3.x, the values in the GcUser’s UserGlobals are used at startup only; runtime changes to these values are done using methods in System class.

Workaround

After reclaimAll, MFC, or Epoch, manually reset these values by executing:
    System setReclaimConfig: configName toValue: theValue

If the desired parameter values are set in the GcUser's UserGlobals, you may also restart the ReclaimGem.


Last updated: 11/12/18