C.1 Estimating processing performance for JP1/AJS3 - Definition Assistant

(1) Recommended configuration

We recommend that you consider the above, and perform the following three operations for JP1/AJS3 - Definition Assistant to mitigate the network load for data transmission, to prevent degradation in performance for processing of the definition information management template and execution command:

• Perform load balancing by separating the machine on which JP1/AJS3 - Definition Assistant is installed from the connection destination JP1/AJS3 - Manager or JP1/AJS2 - Manager machine.

• Perform processing at a time when the JP1/AJS3 - Manager or JP1/AJS2 - Manager machine is not performing operations.

• Divide the processing units so that as few units are processed simultaneously as possible.

Functionally speaking, JP1/AJS3 - Definition Assistant can process definition information for more than 10,000 units simultaneously. However, keeping performance load in mind, we recommend that you keep the maximum number of units processed simultaneously for one operation to around 1,000.

Note that the following definitions significantly lower performance, and should not be made:

• The number of the specified schedule rules for a jobnet is 10 or more.

• The complete unit name is too long.

To Page Top

(2) Estimating the import processing time

Although performance depends on differences in machine specifications, you can generally use the following formula to obtain an approximate time required for importing definition information:

Import-processing-time (seconds) =
            a + (b x 0.1) + (c x 3.5) + d

Legend:

a:

Time required for remote execution of a command

Estimate about 15 seconds. However, you must add additional time when there are many units immediately below the target jobnet.

b:

Total number of units under the specified unit and under all units at the same level as the specified unit

However, when you specify a unit immediately below the root job group, b is the total number of units under the specified unit.

c:

Average number of definition items specified per unit

d:

Time required for saving the execution result file

The following table provides guidelines for how much time is required.

Table C‒1: Guidelines for the time required to save an import execution result file

Execution result file size (unit: megabytes)	Required time (unit: seconds)
2	20
10	60
20	90

To Page Top

(3) Estimating the export processing time

Although performance depends on differences in machine specifications, you can generally use the following formula to obtain an approximate time required for exporting definition information:

Export-processing-time (seconds) =
                         a + (b x 0.1) + (c x 0.01) 
                         + (d x 0.05) + (e x 1.5) + (f x 1.0) + (g x 0.01)
                         + (h x 1.5) + i + 5

Legend:

a:

Time required for remote execution of a command

Estimate about 15 seconds. However, you must add additional time when there are many units immediately below the target jobnet.

b:

Number of jobnets and job groups specified for batch definition

c:

Number of jobs specified for batch definition

d:

Number of units under the uppermost jobnet that are specified for batch definition

e:

Number of units specified for independent definition

f:

Number of modification items specified for modification

g:

Number of units specified for modification

h:

Number of units specified for deletion

i:

Time required for saving the execution result file

The following table provides guidelines for how much time is required.

Table C‒2: Guidelines for the time required to save an export execution result file

Execution result file size (unit: megabytes)	Required time (unit: seconds)
2	20
10	60
20	90

To Page Top

(4) Estimating the ajsdaconvert command processing time

Although performance depends on differences in machine specifications, the following table provides guidelines for how much time is generally required for ajsdaconvert command processing for a file.

Table C‒3: 1General processing time per file

File size (unit: megabytes)	Processing time (unit: seconds)
2	40
10	230

To Page Top