You can improve Engine performance by configuring logging levels and log file size.
When the engine logging level is not configured correctly, it can reduce engine performance. The engine can distignuish between engine log messages and log messages generated by PBL methods.
You can configure the maximum engine log file size as well as the maximum number of log files used by an engine. In general, it is better to have multiple small logs instead of fewer large logs. The time it takes for the file system to write large files can reduce engine performance.
By default the engine log file is set to 2KB.
Setting the logging severity correctly can help engine performance. You should set the logging severity according to the needs of your environment.
In a development environment, you may want to include as much loggin information as possible. However, in a production environment you may only want to generate more severe log messages to reduce log files sizes.
PBL methods can be configured to send messages to the engine log files when events are encountered. To ensure that logs generated by PBL methods are correctly captured in the engine log, you should severity argument of the logMessage method. In the following example the log severity is set to DEBUG.
logMessage "Executing Initial Customer Info" using severity = DEBUG
If the severity level for PBL-generated error messages is set to DEBUG, then this log will appear in the log file. However, if it is set to a higher level, then this message will not appear.