Load Management

Version

Functions

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 notifies O&M personnel through SMS, emails, and platform messages.

Load Management also supports functions like the intelligent control of alive memory sessions, intelligent releasing, template limits, and lifecycle, safeguarding the server stability, as shown in the following figure.

Note:

 If you use the server deployed in WebSphere8.5 or the designer with a built-in JDK11, a prompt appears when you use the Load Management function on the built-in server of the designer: "Technique upgrading. Memory management does not support built-in server. If needed, please use deployed server."

Load Surveillance includes Real-time Load and Intelligent Alert.

Real-time Load

Real-time Load visually displays the memory utilization rate and the CPU utilization rate of the system in the last half hour through charts, as shown in the following figure.

1. Load

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

Therefore, FineReport adds the load analysis chart to reflect the real load situation of JVM. The chart can obtain GC data through GC callbacks and accurately measure various states of the JVM load.

2. Memory Utilization Memory utilization rate = the currently used memory capacity (unit: bytes) / the maximum available memory capacity (namely, the maximum memory capacity that can be assigned to JVM; unit: bytes)

3. CPU Utilization CPU utilization rate is the CPU usage rate 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 determine whether to enable Real-time Load.

Intelligent Alert

Functions

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 sends messages to you after the alert is triggered at 14:00 P.M., it does not send messages to you after the alert is triggered again at 14:03 P.M..

3. Intelligent Alert Notification Content

"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.

Setting an Intelligent Alert

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

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 Reminder

3. Email Reminder

Note:

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

A session is a template in a directory opened by a user in the decision-making system.

Memory Session Display Values

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: displays the number of alive sessions.

• Memory Occupation: displays the occupied memory proportion.

• Number of New Sessions Within 10 Minutes: displays the number of new sessions within 10 minutes.

• Number of Ended Sessions Within 10 Minutes: displays the number of ended sessions within 10 minutes.

End Session

You can select sessions and manually end them. Select the needed sessions and click End Session, as shown in the following figure.

Note:

1. The Recent Access Time field is added on the project V11.0.2 and later versions.

2. If template limits are triggered, the session memory capacity is displayed as 0 KB on the project of versions earlier than V11.0.4. For the project V11.0.4 and later versions, the session memory capacity can be display normally.

• Template Name: displays the report template location and name corresponding to the session.

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

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

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

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

• User: displays the user initiating the current session.

Intelligent Release

Intelligent Report Memory Release

This function can avoid the intervention in the system garbage collection through the deeply-developed load judgment algorithm based on the JVM underlying principles, greatly improving the accuracy and timeliness of the system load judgment.

After the Intelligent Report Memory Release function is enabled, new sessions go to the queue in the case of high load. If the sessions being calculated try to calculate a large amount of data, the attempted calculation is stopped. If the sessions that have finished the calculation for the large amount of data occupy a large amount of memory, the sessions being calculated are stopped.

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 and the function takes 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, ensuring stable system operation and minimizing the impact on users.

Intelligent Memory Release of Report Table

This function is added on the project V1.0.4 and later versions.

After the results are calculated, result tables and the reference objects in the result tables still occupy memory space, which can increase memory pressure.

After the Intelligent Memory Release of Report Table function is enabled, the system can optimize the result table memory of pagination preview templates and optimize the memory of data analysis preview templates that do not use functions like sorting, group filtering, list filtering, and collapse trees.

The Intelligent Memory Release of Report Table function is enabled by default. Click Save and the function takes effect.

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

1. You can set Max Number of Rows Per Dataset, Max Number of Cells Per Template, Max SQL Execution Period (s), Max Number of Cells in Imported Excel, and Record Submission Limit (allowing you to determine whether to allow the generation of Cartesian product). If the set limit is reached, the system rejects the request and pops up a prompt.

2. Template limits include general limits and single limits on some templates.

For details, see Template Limit.

1. Lifecycle detects whether sessions expire or not in a real-time manner.

2. If sessions do not send requests to the backend within X minutes (default value as 30 minutes), they are cleared by the system.

Note:

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