https://wiki.netyce.com/ 2026-05-05T10:47:24+00:00 https://wiki.netyce.com/ https://wiki.netyce.com/lib/exe/fetch.php?media=wiki:logo.png text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:jobs:distr_scheduler&rev=1720009873&do=diff Distributed Scheduler Introduction On NetYCE installations using multiple servers, Jobs scheduled for execution can be directed to specific servers or distributed over targeted servers. By setting up scheduler rules in the designated configuration file practically all situations can be covered using these rules. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:jobs:jobs&rev=1720009873&do=diff Job scheduling text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:jobs:job_configuration&rev=1720009873&do=diff Job Configuration The scheduler and its behaviour for the various job types is fully customizable using an XML file. This file controls the required permissions for the various actions available using the Scheduled jobs tool. But is also includes the queues definitions as used by the scheduler. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:jobs:parallel_jobs&rev=1720009873&do=diff Parallel jobs using multiple queues By default NetYCE uses a single queue, which can run up to 50 jobs in parallel, with a 2 second schedule interval. Example: when you schedule 50 jobs with 1 queue it takes up to a total of 100 seconds for all the jobs to be scheduled. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:jobs:queue_operation&rev=1720009873&do=diff Queue Operation Each NetYCE front-end server uses a job scheduler that can operate several queues. One queue might suffice but assigning some job-types to a separate queue could prevent many small, quick jobs to be kept pending due to one or two lengthy jobs.