Load Management

Version

Function Description

Load Management supports the real-time surveillance and alerts for load, memory, and CPU utilization. If the load reaches the specific bottleneck value, the system will notify you through SMS, emails, or platform messages.

Load Management also supports the intelligent control of the survival, clearance, template limit, and lifecycle of sessions to ensure the stable operation of the server, as shown in the following figure.

Load Surveillance includes Real-time Load and Intelligent Alert.

Real-time Load

The memory utilization and the CPU utilization of the system in the most recent half an hour are displayed through charts, as shown in the following figure.

1. Load

The real load of JVM (Java Virtual Machine) cannot be well reflected through the memory utilization due to the function of the GC (Garbage Collection) mechanism.

Therefore, the load score is introduced in FineReport to reflect the real load of JVM. The GC data can be obtained through GC callbacks. Various states of the JVM load can also be accurately measured.

2. Memory Utilization = Currently used memory/Maximum available memory

Currently used memory: the memory size currently used (unit: bytes)

Maximum available memory: the maximum memory (unit: bytes) that can be allocated to JVM

3. CPU Utilization = CPU utilization during the collection.

Note:

1. The actual server pressure is calculated in Load Surveillance. Memory and CPU surveillance only represent the objective status and cannot accurately reflect the server pressure. It is for reference only.

2. You can enable or disable Real-time Load.

Intelligent Alert

Function Description

1. Triggering Condition

The intelligent alert is triggered if the utilization rates of the old generation are all more than 90% after three consecutive Full GCs.

2. Time Interval Limit

The time intervals between two alerts cannot be less than 5 minutes.

For example, if the system notifies you when the alert is triggered at 14:00 P.M., it does not notify you when the alert is triggered again at 14:03 P.M.

3. Content of the Intelligent Alert Notification

"Hello, the #webname# system #clustername# has too serious overload, which may incur downtime risks. Pay attention to this problem. You are advised to analyze the performance problem of the current system under System Management > Intelligent O&M > Cloud O&M."

Note:

1. #clustername# is empty in the standalone environment.

2. webname is the platform title name.

Intelligent Alert Setting

The Intelligent Alert function is disabled by default. Enable Intelligent Alert as the admin, set Alert Mode to SMS Reminder, Platform Message, or Email Notification, and click Save after completion, as shown in the following figure.

1. SMS Reminder

Note:

To enable SMS Reminder, you need to first enable the Use SMS Platform function. For details, see SMS Service.

2. Platform Message

3. Email Notification

Note:

To enable Email Reminder, you need to first configure the mail server. For details, see Email Service.

A session is a template in a directory you opened in the FineBI system.

Display Values of the Memory Session

The Memory Session page includes Number of Alive Sessions, Memory Occupation, Number of New Sessions Within 10 Minutes, Number of Ended Sessions Within 10 Minutes, and the End Session area.

• Number of Alive Sessions: The number of alive sessions is displayed.

• Memory Occupation: The occupied memory proportion is displayed.

• Number of New Sessions Within 10 Minutes: The number of new sessions within 10 minutes is displayed.

• Number of Ended Sessions Within 10 Minutes: The number of ended sessions within 10 minutes is displayed.

End Session

You can select a session and manually end it. Select the to-be-ended session, and click End Session, as shown in the following figure.

• Object Name: the report template location and name corresponding to the session

• Start Time: the start time (ranked in the ascending order by default) of a memory session

• Recent Access Time: the time when you last refreshed the current session

• Request Duration(s): the survival time of the session (unit: s)

• Memory Size: the memory size occupied by the current session

• Operation: the user's operation on the current session

• User: the user initiating the current session

Intelligent Report Memory Release

The system can avoid intervention during garbage collection through the deeply-developed load judgment algorithm based on the JVM underlying principles, which greatly improves the accuracy and timeliness of the system load judgment.

After the Intelligent Report Memory Release function is enabled, new sessions queue up during high load. The calculations of sessions in the process of calculations will be paused when a large data volume is attempted to be calculated. Sessions, where the calculations have been completed, will be cleared if they occupy too much memory.

The Intelligent Report Memory Release function is enabled by default. You can customize the alert prompt. The default alert prompt is: "The server is overloaded seriously, triggering the protection mechanism. Refresh the page and access the page later."

Click Save to make the function take effect, as shown in the following figure.

Note:

You do not need to set thresholds. The system can intelligently select the most suitable release strategy based on the load status to ensure stable system operation and minimize the impact on users.

Intelligent Memory Release of Report Result Table

After the results are obtained in a report, result tables and the reference objects in the result tables still occupy memory, which can increase memory pressure.

After the Intelligent Memory Release of Report Table function is enabled, the result table memory of pagination preview templates can be optimized. The memory of data analysis preview templates where functions including ranking, group filtering, list filtering, and collapsible trees are not used can also be optimized.

The Intelligent Memory Release of Report Table function is enabled by default. Click Save and the function takes effect, as shown in the following figure.

You may need to set limits for templates with overly complex internal calculation logic which may cause system downtimes.

1. You can set Max Number of Rows Per Dataset, Cell Quantity Limit Per Template, Max SQL Execution Period(s), Cell Limit During Excel Import, and Record Submission Limit. If Record Submission Limit is enabled, you can enable/disable Allow Cartesian Product. When the set limit value is reached, the request will be rejected and a prompt will be displayed.

2. Template Limit includes general limits and separate limits on certain templates.

The Template Limit function only takes effect on FineReport templates in the project. For details, see Template Limit.

1. You can check in real-time whether sessions expire or not.

2. If sessions do not send requests to the backend within X minutes (default value: 60 minutes), the sessions will be cleared by the system.

Note:

The minimum value is 10 minutes and the maximum is 10,000 minutes.