<< Click to Display Table of Contents >> Current:  Create Dashboard  Performance Test

When a user edit a dashboard, the system will check the performance of the dashboard to inform the user of the areas that will affect the display of the dashboard and give reasonable suggestions. Dashboard performance detection reasons are divided into three categories, including system reasons, dashboard reasons and data set reasons, which are described in detail below. When there is a performance problem in the dashboard, a small red dot reminder will appear on the "Performance Help" on the dashboard toolbar, users can click "Performance Help -> Performance Test" to view specific reasons and suggestions, and click "Download" in "Performance Test" to download the reasons for the slow performance are exported in Excel format, as shown in the following figure:

When the user has modified all the problems listed in the performance test according to the suggestions given, the red dot will disappear.

➢Note:

Dashboard performance test is only prompted when the user is editing a dashboard, and not prompt when previewing the dashboard.

 

❖Performance Test Frequency

The frequency of dashboard performance test can be controlled through the db.performance.test.interval property in System Settings-> System Parameters Setting-> Basic Parameter Configuration, as shown in the following figure:

The default value is 60s, that is, the performance of the dashboard is tested every minute. The user can also manually modify the value.

➢Note:

Opening a dashboard for the first time or switching multiple selected dashboard after opening multiple dashboards at the same time will immediately test the performance of the dashboard, and other operations will test by the attribute value.

 

❖Pop-up Performance Test Tips when Saving Dashboard

After the user finishes making the dashboard, click "Save" or "Save As", and the detection performance prompt box will pop up by default to list all the performance problems in the dashboard. The user can modify the dashboard according to the listed reasons and suggestions, as follows the picture shows:

Click "Keep Saving", the dashboard is saved successfully; click "Cancel" or "Close", the user can continue to make the dashboard.

Whether the detection performance prompt pops up when saving the dashboard can be controlled by the db.save.performance.detail property in the system settings -> system parameters setting -> basic parameter configuration, as shown in the following figure:

The attribute value can be true or false, and the default is true. When the value is true, the detection performance prompt box will pop up when saving the dashboard; when the value is false, the detection performance prompt box will not pop up when saving the dashboard, and the user can configure it as needed.

 

❖System Reason

When the user modifies some attribute values related to the amount of data beyond the default value, it may cause too much pressure on the calculation. We will prompt for this and collect the system reasons. For example, the user changes the value of list.qry.maxrow in the System Settings-> System Parameters Setting-> Data Parameters Setting to more than 10000, a prompt will pop up, as shown in the figure below:

After the user clicks "OK" to forcibly modify the value, this information will be collected into the system reason for dashboard edit, as shown in the figure below.

 

❖Dashboard Reason

When the user creates a new column in the dashboard, if the column cannot be pushed down to the database for execution, it will be displayed in orange, and the mouse hovering over the column will have a performance test prompt, as shown in the following figure:

When the dashboard has the following conditions, it will be collected into the dashboard reason:

1) In the SQL data set used on the component, the columns cannot be pushed down to the database for execution, or the filter conditions set in the component's filters cannot be pushed down to the database for execution, as shown in the following figure:

2) The filter component or parameter component has no default value selected and the empty option strategy is set to all data, that is, all data is displayed at once, as shown in the following figure:

3) In the SQL data set used on the component, the columns is listed as a detailed expression of the logical judgment type (the expression has only if statements), as shown in the following figure:

4) There are more than 10 dimension bindings in the component, as shown in the following figure:

5) When there are multiple filter conditions in the dashboard, as shown in the figure below:

6) For databases that already support paging, paging is not used when making a detailed table, as shown in the following figure:

 

❖Data Set Reason

When the data set that the dashboard component depends on (SQL data set / self-service data set / composed data set) has columns or operations that cannot be pushed down to the database or the filter conditions in the Filter of the SQL data set cannot be pushed down to the database, this information will be collected into the data set reason, as shown in the following figure: