Transport Schedules

Following is a brief explanation of the system agents and scheduling guidelines for your transports.

The system executes your transports using a set of agents which allocate a slice of time for each process running in the data center.

As the load increases more agents are added to maintain the level of service. This type of environment is called multi tenant.

In order to maintain fairness among all users, the system detects transports which have high frequency schedules, but no actual activity, and demotes their priority.

You can define wide schedules with frequency as high as every 15 seconds but your transports will only be served at high frequency if the agent actually finds files to process (pull or push).

A few guidelines to setup your transport schedules:

1. When possible, spread the schedules to prevent hot spots.
2. Unless you have a special use case, keep execution frequency at minimum of 5 minutes
3. The schedule window should not be too narrow or too wide. If it is too narrow the agent might not get to it in time. If too wide the agent will have to make redundant checks.

An example of a good schedule is one hour with 5 minute frequency.

See Elevated Priority.