Maintenance
This feature does the following:
1) It requests the Java Virtual Machine to do memory cleanup.
2) It saves user, task and schedule data.
3) Re-launches the Scheduler Engine automatically.
You can create and schedule a Maintenance task weekly/monthly to free memory, if you notice that the memory consumption by the Engine is high. Please create only a single Maintenance task. Make sure that no other task is scheduled, when this task has a scheduled run. Leave at least 1 minute idle time, before this task runs. Generally, you may need to run this task only on Windows and Mac OS. This Maintenance task is also useful, if you are running tasks very frequently (every few seconds), and running out of memory. In this case, you can schedule a Maintenance task more frequently, depending on your needs.
On Solaris and Linux, we have run tasks every 10 seconds for 1 month continuously, without running out of memory, or the engine shutting down. The memory usage, during this accelerated reliability testing, stabilized at a peak of ~50 MB, for the entire 1 month testing period. Normally, the memory usage should cycle up and down between 15-30 MB.
About Memory Usage