1.8

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. PrintShop Mail 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 PrintShop Mail 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.
Page 335