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 machine.

• Perform processing at a time when the JP1/AJS3 - 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) =
    ((0.15*a*b)*(1-i-j)) + (0.01*c) + (0.01*d) + (0.025*e) + (0.001*f) +
    (0.08*g) + h

Legend:

a: Average size of the unit definition

Estimate the size of the standard output file that was obtained by executing the ajsprint -a command for a single unit with the most definition information defined.

b: Number of units

c: Total number of "Open day"

d: Total number of "Closed day"

e: Total number of lines of "Command statement"

f: Total number of a Relations

g: Total number of lines of "Environment variables"

h: Time required for saving the execution result file

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

Table C‒1: Approximate time required to save an import execution results file

Execution result file size (unit: megabytes)	Required time (unit: seconds)
2	10
10	50
20	100

i: If 1 is specified for IMPORT-USEMEMORY, use 0.05 for an estimate. If 0 is specified for IMPORT-USEMEMORY, use 0 for an estimate.

j: If Y is specified for IMPORT-TIME-IMPROVE and the version of JP1/AJS3 at the connection destination is 10-00 or later, use 0.25 for an estimate. If these conditions do not apply, use 0.

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) =
  (0.003*a) + (0.3*b) + (0.02*c) + (0.3*d) + (0.02*e) + (0.02*f)
  + (0.3*g) + h

To Page Top

(4) Estimating the ajsdaconvert command processing time

Although performance depends on differences in machine specifications, you can generally use the following formula to obtain an approximate time required for ajsdaconvert command.

ajsdaconvert command-processing-time (seconds) = (a*(8.5*b) + 5) + 30

Legend:

a: Number of files before conversion

b: File size of the execution result file (megabyte)

Estimate the size of the file by using the execution result file that has the largest size before conversion.

If the above process is difficult, estimate the size by using the following formula:

File size of the execution result file (megabytes) = c*d

c: Average size of the unit definition

Estimate the size of the standard output file that was obtained by executing the ajsprint -a command for a single unit with the most definition information defined.

If the above process is difficult, estimate the size by using the value 0.007.

d: Number of units

If all of the files before conversion are in xls format, estimate the size by using either the value of MAX-IMPORT-UNIT or MAX-EXPORT-UNIT in the environment settings parameters, whichever is larger.

For other formats, estimate the size by using the value of XLSM-MAX-IMPORT-UNIT or XLSM-MAX-EXPORT-UNIT in the environment settings parameters.

To Page Top