Separate Segmentation Recurrence

The SEGMENTATION_GC_TASK recurrence schedules a separate Segmented Assets Cleaner run that cleans up marked segmentation data in asset type workflows. This is the same cleaner run by GC_TASK.

By default, WorldServer marks obsolete segmentation data in asset type workflows for cleanup immediately upon completion or cancellation. In combination with this separate cleaner, WorldServer can reclaim memory and database space more quickly that it would otherwise.

This recurrence also has a default nightly schedule. SDL recommends running it at least as often as the overall GC_TASK recurrence.

User Settings for Data Cleanup

Two user-visible settings let you clean up obsolete data more frequently. Both features are enabled by default for new workflows (existing workflows will not automatically be marked for segmentation cleanup). SDL strongly recommends that you use both new features.

Set the new enabled checkbox for individual workflow properties: Clean up segmentation data at task completion.

The checkbox is available when you view or modify workflows by selecting Management > Workflow > Workflows > [workflow name] .

In asset type workflows, the checkbox marks obsolete segments for cleanup at the next run of the Segmented Assets Cleaner. This cleaner is now run by two recurrences, GC_TASK and SEGMENTATION_GC_TASK.

Note: WorldServer enables this checkbox by default for all new asset type workflows on the system, including any workflows imported from another WorldServer instance. Existing workflows will not be enabled, however. Edit the workflow from Management > Workflow > Workflows > [workflow name] to make this change.

The new column Segmentation Data Marked for Cleanup on the Management > Workflow > Workflows page indicates whether the new setting is enabled for asset type workflows.

Set the new SEGMENTATION_GC_TASK recurrence, as defined on the Management > Business Rule Linkage > Recurrences page.

Note: SDL recommends that you run the new recurrence at least as frequently as the existing GC_TASK recurrence. Select the recurrence name to see the schedule in effect.

While an early-morning daily run of both recurrences is scheduled by default, users can change scheduling by day, date, and hour. Be aware of any other activities that might impact garbage collection, such as database backup.

Recurrence Behavior

By default, SEGMENTATION_GC_TASK runs at the same time and on the same schedule as GC_TASK. If one of the recurrences should happen to try to run the Segmented Assets Cleaner at the same time, the second task would back off. There are two possible results:

If GC_TASK is running, and SEGMENTATION_GC_TASK tries to run, the second task exits and will try again at its normally scheduled time.
If SEGMENTATION_GC_TASK is running, and GC_TASK tries to run the Segmented Assets Cleaner second, GC_TASK skips that cleaner and proceeds to the next cleaner in its list.