1. SET RUN
TIME CLOCK RESOLUTION HIGH.
2. SET RUN TIME CLOCK RESOLUTION LOW.
Use this statement to specify the precision with which the value of the runtime is returned when the GET RUN TIME statement is executed:
If you are using long measurement intervals (that is, per second or longer), low precision is usually sufficient. Runtime analysis is correct on all platforms for both single processors and multi-processors.
If you are using short measurements (less than seconds) you should use high precision, depending on the machine type and number of processors.
The following platforms support high precision measurement for either one processor or multi-processors. (For the exceptions to this rule, see the note below):
The following platforms support high precision measurement only for one processor; with multi-processors, values may be false:
On these platforms, time measurement is based on a hardware register connected to the CPU. There is
no synchronization of these registers between the different processors. This means that values are incorrect
if you change processors. When measuring the runtime of smaller program
components, you can achieve the correct result by taking several measurements and using the minimum of these.
If you specify high precision measurement and the measurement interval cannot consequently be represented in the processor register, time values will be false (see
'Utilities -> Measurement interval...').
SET RUN TIME CLOCK RESOLUTION HIGH.
High precision is used with a short measurement interval when the GET RUN TIME statement is executed.
SET RUN TIME CLOCK RESOLUTION LOW.
Low precision is used with a long measurement interval when the GET RUN TIME statement is executed.
Non-Catchable Exceptions
Measuring the Runtime of Program Segments