Configure RML Engine Timeout and Chunk Settings in Repertoire 202x

Repertoire 2022+
1

Overview

This guide outlines how to configure timeout and chunk management parameters for the RML engine in Repertoire 202x. These settings help optimize report rendering performance and manage resource usage.

Step 1: Locate the Configuration File

Navigate to the /etc folder within your Repertoire 202x installation directory and locate the application.conf file.

Step 2: Configure RML Engine Timeout and Chunk Settings

Within the application.conf file, add or update the following block under the ambience.rml-engine section:

ambience.rml-engine {
  default-timeout: 60 seconds
  large-chunk-expiry: 2 hours
  large-chunk-size: 1K
  ...
}

Parameter Breakdown:

  • default-timeout: 60 seconds
    Sets the maximum time allowed for rendering a report before timing out.

  • large-chunk-expiry: 2 hours
    Specifies how long large report chunks are retained before being purged from the system.

  • large-chunk-size: 1K
    Determines how big the rendered report files are retained before being cleared to prevent the Codex folder buildup.
    As a best practice, ensure the JobQueue file size remains under 100MB to maintain system stability and avoid resource strain.

These settings are particularly useful in environments with high report volume or large output files, helping prevent accumulation in the Codex folder and reducing potential performance bottlenecks. You may adjust these values based on your system’s available memory, report complexity, and expected workload levels.

Step 3: Save and Restart

  1. Save your changes to the script.
  2. Restart the Repertoire server to apply the updated configuration.

Step 4: Verify Configuration

After restarting:

  • Monitor the Codex folder to ensure large chunks are being cleared as expected.
  • Validate report rendering performance under typical load conditions.