7.1 Notes on the number of root jobnets registered for execution

Without taking into account available disk and memory resources and processing performance, the maximum number of root jobnets that can be registered for execution in theory is 2,147,483,647. As long as four thousand root jobnets are registered in JP1/AJS3, there must be no functional problem. However, when executing jobnets and jobs in JP1/AJS3, consider the following points from a performance viewpoint.

• Notes on defining thousands of root jobnets in one hierarchy level

  If 4,000 root jobnets are defined in one hierarchy level, system performance might suffer. Take the following measures if necessary. These measures assist not only execution performance, but also GUI-based monitoring and command performance.

  • When there are a large number of root jobnets that contain only a few units, aggregate the units into as few root jobnets as possible.

  • Arrange job groups into hierarchies.

    Do not group more than 500 root jobnets, including nested root jobnets, in one job group.

  • Consider the following points about the jobnets you register:

    - Provide 2 or 3 levels of hierarchy, including the root jobnet.

    - Define no more than 50 to 80 nested jobnets and jobs in the hierarchy below one root jobnet or nested jobnet.

    - Make sure that no more than approximately 500 nested jobnets and jobs are located below one root jobnet.

  • Divide the root jobnets so that no more than approximately 4,000 root jobnets are registered for execution by the scheduler service, and then run multiple scheduler services.

• Other notes

  • If you specify a number of logs to keep, number-of-logs-to-keep x number-of-registered-root-jobnets is used as the number of registered root jobnets for disk capacity management and resource management purposes. Therefore, be careful about the disk capacity and other resource management items.

  • Although a large number of root jobnets can be registered, this does not mean that a large number of jobs can be executed concurrently. When you design a work task, be careful about system resources and processing performance. For example, when designing a work task that uses a large number of jobs, design the work task so that there is no time period where a large number of jobs are required to run concurrently.

  • Design work tasks with a view to distributing tasks to more than one time period and CPU.

  • When many root jobnets are defined, consider root jobnet registration methods (all or divided), registration time, time for start-up, and performance of commands for batch definition, operation, and display.

  • If you register a large number of root jobnets for execution, release, or a cancellation of release within a short period, and you specify a long fixed schedule period for fixed execution registration, the system load might temporarily spike, delaying execution of root jobnet generations created when start conditions are satisfied.

    If you want to register many root jobnets for execution, release, or a cancellation of release, reduce the number of root jobnets you register at one time. If you want to register a root jobnet for fixed execution, shorten the fixed schedule period to reduce the load on the system.

  • Defining a large number of jobnets or jobs in one root jobnet, or using too many relation settings, could cause a deterioration in operability and performance of JP1/AJS3 - View and JP1/AJS3 - Web Console. To maintain operability and performance, the jobnet should have two or three hierarchy levels, and each root jobnet and nested jobnet should have about 50 to 80 units.

To Page Top