Limit In-Memory Log Output

PDI logs data about transformations and jobs according to default parameters that control how many lines are allowed in the log and how long the oldest line should stay in memory before it is released. Obviously the more lines that are recorded and the longer they are kept, the more heap space is consumed by them. If you are experiencing memory shortages or slow performance in your PDI content, you can address the problem by modifying in-memory logging.

In Spoon, the following parameters control logging:

• KETTLE_MAX_LOG_SIZE_IN_LINES, which sets the maximum number of log lines that are kept internally by Kettle. Setting this to 0 (the default) forces PDI to keep all rows.
• KETTLE_MAX_LOG_TIMEOUT_IN_MINUTES, which represents the maximum age (in minutes) that a log line should be kept internally by PDI. Setting this to 0 (the default) keeps all rows indefinitely.
• KETTLE_MAX_JOB_TRACKER_SIZE, which sets the maximum number of job trackers kept in memory. Default value is 1000.
• KETTLE_MAX_JOB_ENTRIES_LOGGED, which sets the maximum number of job entry results kept in memory for logging purposes. Default value is 1000.
• KETTLE_MAX_LOGGING_REGISTRY_SIZE, which sets the maximum number of logging registry entries kept in memory for logging purposes. Default value is 1000.

The equivalent parameters to the first two variables, which can be set on each KTR or KJB individually using Kitchen or Pan, are:

• maxloglines
• maxlogtimeout

Set these values to the lowest non-zero values that your operations can tolerate. If you are using logging for any purpose, you must balance between tolerable performance and necessary functionality.