Garbage collection

WorldServer creates database objects to represent various elements such as projects, tasks, or segmented documents. To reclaim database space, WorldServer uses cleaners to delete obsolete objects periodically, in a process known as garbage collection.

Certain created objects are deleted as soon as they become obsolete, but most are not. This is because deleting objects can be a time-consuming procedure that requires a lot of resources. Also, in certain cases, it is not always immediately clear when an object becomes obsolete.

For example, when an asset is segmented, it is stored in a structure that is used internally until the source asset is modified. When the asset is modified, a new segmented document structure is created and the old one is left in the database and marked for garbage collection.

Garbage collection consists of several cleaners, each of which cleans up a particular area of the WorldServer schema. If you want, you can schedule each cleaner to run separately by going to Management > Administration > Garbage Collection. By default, WorldServer garbage collection is scheduled to run every night.
  • On stand-alone WorldServer instances, schedule changes are updated automatically.
  • In clustered WorldServer environments, you must restart the other WorldServer instances for the schedule changes to be applied.