We have recently reviewed new default tuning parameters for all new Board Cloud instances across versions 12 and 14.
These parameters are designed to:
- Improve overall system performance
- Prevent unexpected resource saturations
Together, these defaults help optimize the performance and reliability of your Board applications.
Overview of the Default Tuning Parameters
Parameter | Default Value | Available for the Board version | Purpose |
|---|
MaxRowsUpperLimit | 100000 | 12, 14 | Controls the maximum number of rows returned from Engine to Client, helping prevent layout failures |
LayoutResponseMaxCells | 2000000 | 12, 14 | Limits the total number of cells processed in a layout to reduce the risk of memory overload. |
MaxCombinationToEvaluate | 268435455 | 14 | Restricts the total number of elements (rows × columns) displayed in a layout to protect system performance. If the requested size exceeds the defined limit, the layout will not be executed preemptively, ensuring that no memory is allocated on the server |
LayoutExecutionMinutesTimeout | 5 | 12, 14 | Sets the maximum execution time (in minutes) for a layout before the process is automatically stopped. |
Note: These limits apply to all objects with layouts, except Dataflows, FlexGrid objects, and Export datasets. Please note that only the Board Support Team can change these parameters.
Description of the parameters
2.1 MaxRowsUpperLimit
Purpose: Defines the maximum number of rows that can be transferred from the Engine to the Client.
Behavior: If a layout exceeds this limit, the system provides log messages indicating whether the layout was canceled, failed, or completed due to the threshold. This helps administrators in quickly identifying problematic layouts and apply corrective actions, optimizing application performance and simplifying troubleshooting.
2.2 LayoutResponseMaxCells (Web Engine Level)
Purpose: Prevents excessive memory consumption caused by operations such as Quick Layouts.
Behavior: By limiting the total number of cells processed (e.g., 2,000,000), layouts stay within safe memory boundaries, ensuring stable performance and preventing overconsumption of system resources.
2.4 MaxCombinationToEvaluate (Engine Level – from version 14.2)
Purpose: Defines the maximum layout size (rows × columns) that can be rendered before execution is halted.
Behavior:
- If the layout exceeds the defined limit, execution stops immediately — no memory is allocated on the server.
- The following user message is displayed:
“The requested Layout exceeds the maximum cell limit. To continue, reduce the amount of data in this Layout or contact your System Administrator.”
Diagnostic Logging: Detailed diagnostic logs include InternalRows, InternalColumns, and InternalQuota for precise sizing insights.
Default and Performance Impact: The default value (268,435,455) ensures responsive performance.Increasing this limit could result in:
- Slower performance
- System-wide alerts about resource consumption
- Degraded user experience
3. Changing Default Values
If you believe it’s necessary to modify any of these tuning parameters:
- Open a ticket with the Board Support Team.
- Provide justification and context (e.g., application complexity, data volume, or performance needs).
- The Support Team will review your request and confirm the most appropriate settings.
