...
- Minimal memory footprint (it uses <1k per profile entry).
- Minimal performance impact (less than 2% cpu speed if of added CPU usage when activated).
- Since sampling performance was always there, there is no additional runtime overhead for that, just memory profiling needed to be added.
- Only uses CPU time when the panel is active.
...
Overview
|
|
| Settings |
...
| : |
...
| Toggles between timing and memory profiling. | |
| Workflow Reference Time |
...
: Enter a value in milliseconds which is used to draw the |
...
Workflow timing bar |
...
(default = 20 ms, meaning 50 executions per second). |
...
|
...
|
...
| Workflow |
...
: Shows the workflow name and the total execution time or memory consumption, depending on the profile type setting.
|
...
|
...
| Units: For each |
...
Unit in the |
...
active Workflow there's an entry describing the |
...
Unit's performance, either execution time or memory consumption. |
...
Variables and Published Input/Output |
...
Units are excluded from that list. |
...
The list is selectable and supports multiple and disjoint selections. If one or more |
...
Units are selected in the list, the corresponding |
...
Units are selected in the |
...
Workflow view, and vice versa.
|
...
|
...
|
...
|
...
|
...
Example of the profiler set to profile memory consumption:
...