2019.2

running both clean-up and production jobs simultaneously. If experience
suggests that the clean-up is not running efficiently, then upping the
number of threads here would be recommended. Conversely, if
production appears to be suffering courtesy of the clean-up process,
then reduce the number of threads here.
In general, higher end machines (those with multiple cores) will allow a
higher numbers of threads, whilst low end machines will perform better
with a lower number of threads.
l
Number of entities in each deletion batch: The number of entities to be
deleted at a time. This is done to break the clean-up into smaller chunks. This
improves PlanetPress Connect clean-up responsiveness, whilst the clean-up
is occurring.
The number selected here applies to all the following settings.
i.e. a selection of 1,000 would delete 1,000 data records within a Data Set,
1,000 content items within a Content Set, and so on.
l
Minimum time to retain Data Sets: The minimum time a Data Set (and all the
records it contains) is retained within the database before being set for
deletion.
Tip
In order to prevent attempts at deleting database objects which might
still be in use, it is recommended that all Minimum time retention values
should always be set to at least the length of your longest job. Preferably
with some extra time added, for good measure.
For example, if your longest job takes 45 to 50 minutes to run, then set
the retention time to 55 minutes (or 1 hour) to ensure that all the
database objects created during job processing survive for the duration
of the job.
l
Minimum time to retain Content Sets: The minimum time a Content Set (and
Page 830