This page has been translated automatically.
Setting Up Development Environment
Usage Examples
High-Level Systems
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine and Tools
Double Precision Coordinates
Common Functionality
Controls-Related Classes
Engine-Related Classes
Filesystem Functionality
GUI-Related Classes
Math Functionality
Node-Related Classes
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
Rendering-Related Classes
Warning! This version of documentation is OUTDATED, as it describes an older SDK version! Please switch to the documentation for the latest SDK version.
Warning! This version of documentation describes an old SDK version which is no longer supported! Please upgrade to the latest SDK version.

Performance Analyzer

A number of console commands are available for analizing performance of the scripts and the engine.

Per-function analysis can be output into the console or logged to a file (if its name is specified as a command argument, for example world_analyze new_file.txt

Performance analyzer results are valid only in a single-threaded mode. If threading for any module is enabled (world, physics or pathfinding), values of counters will not be correct.

Logged Data

Data logged by analyzers includes the following:

  • total seconds — the total number of seconds the interpreter spent executing this function.
  • self seconds — the number of seconds accounted for by this function alone, without internal calls of other functions.
  • calls — the total number of times the function was called.
  • total ms/call — the average number of milliseconds spent in this function and its descendants per call.
  • self ms/call — the average number of milliseconds spent in this function per call.
  • name — function name.
Last update: 2017-07-03
Build: ()