Performance issues
When jobs run slowly or durations creep up — what to tune and what's outside FileAgent's control.
Last updated July 17, 2026
#Common causes
- Network and endpoint speed. Practical throughput is governed by the link and the source/destination systems, not FileAgent itself.
- Host placement. Files flow through the FileAgent host — place it near the largest data source to keep traffic local.
- Growing data sets. Durations that creep up usually mean more files or larger files over time.
- Stacked schedules. Many heavy jobs at the same minute compete for bandwidth.
#What to tune
- Narrow the scope. Point jobs at the most specific folder/prefix and use a file pattern so each run handles less.
- Split big jobs into several smaller ones with independent schedules.
- Stagger schedules so heavy jobs don't all start together.
- Raise timeouts and enable retries for very large files over slow links (see reliability).
#Runs overlapping or skipped
If a job is still running when its next window arrives, the new run may be skipped to avoid overlap. Lengthen the interval or shorten the job (narrower scope, split work) so each run finishes comfortably before the next.