...
Size of data packet
- One of major factor affecting data packet sent back by JobScheduler depend upon number JobScheduler objects e.g. job chain, job, order, deployed in live folder.
Number of running jobs/tasks
- Number of running jobs/tasks also add addition run time information e.g. start time, end time, step text etc.
Number of history entries per order/task
- In JOC user can configure how many order/task histories he want to see. As number of order/task history is higher, JobScheduler engine needs more time to fetch that information from database. Also the data packet size will be bigger.
Auto update frequency
- By default auto update of JOC is disabled . But if user enable the Auto update
Database performance
- JobScheduler fetch history and status information from Database tables, as time progress database tables become too big and usual database performance problems such as no indexing, unoptimized queries plans etc started affecting JOC performance.
Network performance
- The JOC communicate with JobScheeduler over LAN / local network. Usually enterprise networks are very fast but added layer of security. packet firewalls, zoned network etc add bit of latency. which also can affect the JOC performance.
JOC Performance Debugging
...