If an adTempus File Trigger is being used to watch a folder with a large number of files, the adTempus server process (adtempusservice.exe) may frequently or continually use close to 100% of CPU time, and/or jobs may not be triggered for file changes in a timely manner.
This problem has been observed in one installation where the folder being monitored contained 25,000 files. The File Trigger works by scanning the target folder(s) at the interval specified in the Polling Interval setting for the trigger. With a very large number of files to scan (and especially if the polling interval is low), adTempus will use a large amount of CPU time completing each scan.
Even if the polling interval is not low, it may still take the File Trigger many minutes (or tens of minutes) to scan very large folders. Because adTempus only evaluates one trigger at a time, this can cause a delay before adTempus starts jobs for other File Triggers.
To avoid this problem, ensure that adTempus is not monitoring folders with large number of files.
The recommended configuration is for adTempus to monitor a "trigger" folder that contains only unprocessed files. Once the job is triggered, the job (or your task) should move the trigger file(s) to a different folder if they need to be retained.
This issue has been resolved. Resolved in version 4.7.