UnigineEditor
Interface Overview
Assets Workflow
Settings and Preferences
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Landscape Tool
Using Editor Tools for Specific Tasks
FAQ
Программирование
Fundamentals
Setting Up Development Environment
Usage Examples
UnigineScript
C++
C#
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine and Tools
GUI
Double Precision Coordinates
API
Containers
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
CIGI Client Plugin
Rendering-Related Classes

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

Notice
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: 27.12.2018