Performance Meter

You may use this Debugger to evaluate the speed of the entire configuration or its part. You may measure the usage frequency for specific code areas and execution speed.

Use the "Debug — Performance Meter command to measure performance. When you run this command again, the measurement will stop, and the measurement results window will open.

Measurement results contain references to specific module lines that specify the frequency and length of execution. They are displayed as a table box with the following columns:





contains the module name;

Line number

module line number


module line text

Usage count

number of line calls during measurement


total time (in seconds) of the execution of this line during measurement;


percentage of the total execution time for this line in relation to the total measurement time (total measurement time equals the sum of all time periods when the configuration code was executed), while the code execution time on the client is taken as 100%.


code lines executing on the client are marked by icon;


code lines executing on the server are marked by icon;

Processing server

code strings that initiate server calls are marked by icons:
  - the server was called at the platform level, or the procedures and functions executed on the server were called directly;
  - a local call of a procedure or function executed on the client contains a server call at the platform level or direct calls of the procedures or functions executed on the server;

Note. If the code line contains a server call or a local call of a procedure or function executed on the client (for example,
A = Function1(Function2()), where Function1 containing the server call is executed on the client, and Function2 is executed on the server), the column will display the icon .

Execution time for each line in execution measurement results is made up of time of operator line execution (net time) and of procedure (function) call time if they are in the line. Use "Include execution time for procedure and function calls" to select which time to indicate: full time (as a sum of call time and net time) or net time of execution.

If the line contains at least one procedure (function) call, the execution time contains operator line execution and procedure (function) call time.

If the flag is checked, the procedure (function) call time is counted in the full execution time.

If this flag is unchecked, the measurement results will include only the execution time for the code line, but not the execution time of the procedure (function) that is called by this line. In this case, the total execution time for this line (in Time column) will not be the same as the actual time spent by the system in processing this line: You have to remember that in general case the execution of called procedure (function) may take a long time and this time will not be included in the result (net time).

The flag is checked by default and its state is recorded between sessions. If the state is changed the time columns names are also changed.

If the Client flag is checked, results of code execution measurement on the client will be displayed.

If the Server flag is checked, results of code execution measurement on the server will be displayed.

If the Client and Server flags are both checked, results of code execution measurement on the client and on the server will be displayed.

Flags are indicated only during server infobase debugging.

Flags are available only during server debug item debugging.

If there are several open windows with performance measurement results, when you place the mouse pointer onto the results column, you will see a tooltip with the URL of the file reflected in this column.

When you double click the mouse on the column with the performance measurement results, the module editor will move to the appropriate string in the file with the performance measurement results.

1C:Enterprise Developer's Community