Performance data model and content

The performance data is stored in a single, de-normalized, repository table named TRON_PERFORMANCE. This section describes the information included.

Events

The performance log is based on events. For each event the starting time (in three variations: a full timestamp, a date, and a time) and the duration (in ms) is stored. The description of an event is made up by a class, a name and a text. Some events have a result (like succeeded or failed). In addition you will find information about the engine that reported an event.

The following list gives a short description of the reported events:

Class

Name

Description

control

execute job

Total execution time of a job (1 record per job execution, duration in attribute PRF_JOB_DURATION (Job Duration in ms)).

init

load job

Get job definition from repository.

process

prepare job

Perform job pre-processing.

process

prepare project

Perform pre-processing for a project within a job.

process

finish project

Perform pre-processing for a project within a job.

control

execute project

Total execution time of a project (1 record per project execution, duration in attribute PRF_PRJ_DURATION [Project Duration in ms]).

init

load project

Get project definition from repository.

init

create

Create project and component instances.

init

configure

Configure project and component instances.

perform

prepare

Perform component pre-processing.

perform

process

Perform component step.

perform

finish

Perform component post-processing.

perform

read

Get data to component input port.

perform

write

Push data from component output port.

finish

close

Close project and component instances.

NoteDue to distributed, multi-threading the total project execution time can be significantly lower than the sum of the execution time of all participating components.

General information

Each execution of project or job is identified by a global unique ID. You will find the execution starting time in three variations: a full timestamp, a date, and a time. Additional information is provided about the account that initiated the execution and the repository the project or job is located in.

Job execution information

For a job you will find the ID, the version (modification date), and the name. A single job execution event will store the duration of a job (in minutes). The components (projects) of a job are represented by their ID, class, and version.

Project execution information (including job projects)

For each executed project ID, version (modification date), name, and a global, unique execution ID is provided. A single project execution event will store the duration of a project (in minutes).

Project components are represented by ID, name, class, type, and version. The process event will provide the number of steps and the amount of processed records.

Port events provide the ID, name, class, type and the amount of input or output blocks and records.