The performance diagnosis feature is a key tool used to analyze and optimize performance. You can use the performance diagnosis feature to identify and resolve performance issues in reports and data analysis operations, improve the speed and response performance of report queries, and improve the efficiency and accuracy of data analysis.
Limits
The performance diagnosis feature is supported only by the dashboard module.
Prerequisites
A dashboard is created. For more information, see Create a dashboard.
A dataset is selected and chart fields are configured. For more information, see Configure a chart.
Procedure
Performance diagnosis portal
After the dashboard is created, click Performance Diagnosis as shown in the following figure.
After you click Performance Diagnosis, the performance diagnosis information of this report is displayed on the right side of the dashboard.
Component performance diagnosis entry
Click the icon to the right of a component and follow the steps shown in the figure to go to the component performance diagnosis page.
After you enter Performance Diagnostics on the dashboard, click a chart in the Component Loading Duration column. The Component Loading Details page appears.
Features
The First Screen Opening Duration indicates the duration that is required to open the report and render the first-screen chart. You can use the First Screen Opening Duration and Risk Benchmark Assessment parameters to determine the performance risk of the report.
If a report contains factors that may affect performance, Performance Diagnosis provides specific optimization suggestions. You can optimize the report based on the descriptions to improve the report loading speed. The Component Loading Time Ranking section lists the component loading time in the report.
Click a chart in the Component Loading Duration column to go to the Component Loading Details page.
Parameter
Description
Query a training dataset
The name of the dataset used by the current chart.
Data Source Type
The type of the data source used by the current chart, for example, mysql.
After you click Query Details, you can view information such as the data source duration, query diagnosis, and query optimization suggestions.
Fast query cache
Query cache: Dataset caching accelerates report access and reduces database pressure.
If it is not open, the following figure shows the "go to open" option.
Actual Query Links
The actual query link of the chart data, for example, a direct database connection.
Top Duration Links
The longest-consuming link and its corresponding duration during data query and data processing, for example:
Specification recommendations
When you edit a dashboard, if you perform operations that may affect the performance of the report, such as adding too many charts or tab widgets, the Performance Diagnosis section displays the number of risk items.
When you create a module, if the number of components is too large, an error is reported as shown in the following figure.
and displays optimization suggestions in the performance diagnosis list.
To ensure the performance and smoothness of the report, we recommend that you do not exceed the following specifications when you build a report:
Category
Description
Recommended value of specifications
Use the dashboard
chart-components
The number of charts and controls is less than 100.
map
The number of maps is less than 2.
Tab label
The number of tab labels is less than 50.
Cross table fields
The number of cross table fields is less than 100.
Schedule Field
The schedule has less than 100 fields.
Indicates the trend chart field.
Indicator trend charts are less than 100.
iframe
The number of embedded pages is less than 5.
Filter Bar
The number of query control elements is less than 100.