Memory Management

1. Version 

2. Function introduction

Including real-time monitoring and early warning of memory and CPU utilization, when memory reaches the specified bottleneck value, it will trigger reminders of SMS, email, message, etc.

In addition, it also supports intelligent control of session survival, clearing, template restriction, life cycle, etc., to ensure the stable operation of the server. As shown below:

The memory warning includes two parts: "real-time memory" and "smart warning".

1. Real-time memory

Use the chart to visually display the memory utilization and CPU utilization of the current system in the most recent half hour, as shown in the following figure:

1) Memory utilization = currently used memory / maximum memory that can be used
currently used memory: current memory size (bytes)
maximum memory: maximum memory that can be used (bytes), the maximum memory allocated to the JVM

2) CPU utilization = CPU utilization at the time of collection

Note: For BI projects of version 5.1.13 and later, the "Real-time memory" switch button has been added to support user-defined switching of this function.

2. Intelligent early warning

Condition of smart warning trigger: three consecutive times After fullgc , the usage rate of the old age is above 90%

1) Enable Smart Alert

The smart alert function is disabled by default.

Turn on the Smart Alert button, as shown in the following figure:

2) Setting the warning mode

1) Intelligent warning time interval limit

The time interval between two warnings shall not be less than 5 minutes.

For example: at 14:00 the warning condition is met, a notification is triggered, and at 14:03 the warning condition is met again , but no notification is made this time.

2) Contents of intelligent early warning notification

Hello, #webname#system#clustername#The current load status is too high, there may be downtime risks, please pay attention in time. It is recommended to use the management system - intelligent operation and maintenance - cloud operation and maintenance function to analyze the performance problems of the current system.

Note 1: #clustername# is empty in the case of a single machine.

Note 2: webname is a variable representing the platform title name.

3) Intelligent early warning reminder

1) SMS reminder:

Note: This function needs to open the SMS platform, click SMS for details

2) Platform information:

3 ) Email reminder:

Note: This function needs to configure the mail server, click the mailbox for details

The memory session interface includes the number of surviving sessions, the percentage of memory usage, the number of new sessions in the last 10 minutes, the number of ended sessions in the last 10 minutes, and options for ending sessions. As shown below:

1. In-memory session display value

Live Sessions: The number of sessions that are still alive

Survival session memory ratio: Indicates the used memory ratio

New sessions in the last 10 minutes: literally

Sessions ended in the last 10 minutes: literally

2. End the session

By default, they are sorted in ascending order by "Start Time".

Support to select, manually force to kill Session. Check the session you want to end and click End Session . As shown below:

Note: The end session function is currently not supported in FineBI5.1 version.

1. Release mechanism

1) Load judgment

Instead of using forced GC, a load judgment algorithm developed based on the underlying principles of the JVM is used to avoid intervention in system garbage collection and greatly improve the accuracy and timeliness of system load judgment.

2) Dynamic release

Under high load, new sessions enter the queue. If a session that is being calculated tries to calculate a large amount of data, the calculation will be stopped . If a session that has been calculated occupies a large amount of memory, it will be cleared.

Intelligent release no longer requires users to set various thresholds. The system intelligently selects the most suitable release strategy according to the load state, ensuring the stable operation of the system and minimizing the impact on users.

2. Specific configuration

Smart release is enabled by default, as shown in the following figure:

Template restrictions include general restrictions and partial template individual restrictions.

The template restriction function only takes effect for the FineReport template in the project.

1. General Restrictions

can limit the maximum number of rows in a single data set , limit the maximum number of cells in a template, limit the maximum execution time of SQL, limit the maximum number of cells when importing into Excel, and limit the number of records submitted. After the number of submitted records, you can also set whether to allow the Cartesian product to be generated by filling in the report. When the set number is reached, the request is rejected and a prompt is given.

"Submit Record Limit" is disabled by default, and the other four items are enabled by default. The default values are shown in the following figure:

1) Real-time detection of session expiration.

2) If the session does not send a request to the background for more than x minutes, it will be cleared by the system. Default is 30 minutes

Note: The minimum allowed is 10 minutes and the maximum is 10000 minutes.