2018.1

l
Product managing the service: Select which of the applications will run the service.
Note
The Server Engine is set as the default as it is generally considered the best
option.
This is particularly the case when using a scheduled cron job, as the Sever Engine
is always running, whilst the Designer might well not be at the scheduled time (in
which case the clean-up will fail to run).
l
Database Clean-up Service:
l
Allow database clean-up service: Select this checkbox to enable the database
Clean-up settings, and enable the actual clean-up.
l
Threads to use for database deletions: The number of Threads to be used
in the clean-up. PlanetPress Connect is a multi-threaded application, and the
clean-up is likewise.
Tip
The default number of threads is considered the best compromise for
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.
Page 86