Versions Compared

Version Old Version 3 New Version Current
Changes made by

Thomas Staiger

Thomas Staiger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Minimal memory footprint (it uses <1k per profile entry).
  • Minimal performance impact (less than 2% 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

workflowProfilerImage Added

Gliffy
name

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).

  • Increasing the value: The workflow timing profile bar gets recalculated and will be smaller.
  • Decreasing the value: The workflow timing profile bar gets recalculated and will be larger.

Workflow: Shows the workflow name and the total execution time or memory consumption, depending on the profile type setting.

Info

The Workflow memory performance bar is calculated relative to the total memory assigned to the JVM. It should always be pretty small.

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.

Info
The Unit performance bars are relative to the Workflow performance. A Unit profile bar going fully to the right to red does not necessarily mean a bad thing – it just means that it consumes most of the workflow execution time or memory used.