Table of Contents

Search

  1. Preface
  2. Introduction
  3. Dashboard
  4. Resources
  5. Workflows
  6. Task Reference
  7. Services Overview
  8. Users
  9. Logs and Reports
  10. Encryption
  11. System
  12. Appendix
  13. Glossary Terms

Performance Considerations

Performance Considerations

Each time a Monitor runs, system resources are utilized to scan folders and compare snapshots. Scanning a folder with a couple files only takes a few milliseconds and minimal system resources. On the other hand, if hundreds of Monitors are set to run every 15 seconds with thousands of files in each folder, the performance impact on the server should be taken into consideration.
The number of active Monitors can be limited by changing the Maximum Concurrent Monitors (located on the Runtime tab in the Global Settings). When a Monitor starts a Project, the Monitor remains active while the Project is running. Setting the Maximum Concurrent Monitors to 1 only allows one Monitor to run at a time. If the Project being executed takes a long time to process, this may undesirably delay the execution of the other Monitors. The default Maximum Concurrent Monitors is 20.
To determine which monitors are actively running and how long they are processing, set the Global Log Level to Debug (located on the Global Log tab in the Log Settings). In Debug mode, a log record is written each time a Monitor is submitted and when a Monitor completes along with the time taken.

0 COMMENTS

We’d like to hear from you!