2020.1

l
Speed: The actual speed achieved (in pages per minute) in this print job. The
speed is calculated by dividing Job size by Duration.
l
Message:
l When no message is shown, this is because the job was too short to make any
sensible statement about it. This happens when the duration is below 30 seconds.
l "Your job ran at the licensed speed." When this message is shown, the achieved
speed for this job is within a 5% margin of the licensed speed. To increase the
licensed speed, look into the different upgrading options (performance packs, or a
product upgrade).
l "Your job did not run at the licensed speed. Press the help button for tips on
improving performance." When this message is shown, it was not possible to
achieve the licensed speed. If performance is an issue, please refer to the topic
about improving performance: "Performance Considerations" on page25.
Profile Scripts dialog
The Script Profiler is accessible through the Context >Profile Scripts menu option. It runs the
scripts in the template, using the current record, in order to verify the speed at which scripts in
the "Scripts pane" on page557 execute. It helps greatly in troubleshooting performance issues
caused by scripting (see also: "Testing scripts" on page387).
When the dialog opens, the script profiler runs automatically, on 1000 instances of all the
scripts by default (this can be changed through the "Scripting preferences" on page376).
Note
The script profiler can take a while, so please be patient.
The results are shown as follows (the first in the line is indicated as Total and represents the
totals of all the scripts underneath, representing a good overview of the scripts performance in
the template):
l
Name: The name of the script being executed.
l
Count: As the profiler runs, Count shows the current number of iterations that have been
run. This goes up to the total number of set instances and then stops. Hover with your
Page 497