Template Performance

Version

Application Scenario

You serve as an administrator responsible for managing FanRuan applications. While projects operate within acceptable parameters, you have encountered persistent performance-related issues reported by business users, specifically concerning template functionality. These issues manifest as preview freezing, prolonged loading time, and noticeable latency during operation.

You need to identify the root causes of slow-performing templates by addressing:

• Which templates exhibit slow performance?

• At which stage does the slowdown occur?

• Which functions contribute to the performance degradation?

• What data queries are causing the delays?

Only by pinpointing the underlying causes of these performance issues can you implement targeted optimizations to enhance user experience and mitigate risks caused by excessive system loads.

Function Description

FineOps provides a Template Performance function, which can help you (the admin) improve:

1. Development efficiency: This feature enhances the efficiency of template performance detection and troubleshooting, thereby accelerating the development of business personnel.

2. User satisfaction: By improving system stability and optimizing the end-user experience, this function contributes to higher levels of user satisfaction.

3. Cost-effectiveness: This function identifies and addresses performance issues at their source and offers comprehensive diagnostic insights, reducing the performance maintenance costs for admins.

1. This function is supported exclusively for FineReport general reports, FineReport dashboards, and FineBI dashboards opened on the PC desktop.

2. You have enabled the Tracing function and configured global settings before using this function.

For details, see Prerequisites for Using Tracing.

3. You have configured Slow Request Standard in Tracing. Only requests with a response time exceeding the set threshold are classified as slow requests.

• Log in to FineOps as the admin, choose Setting > Tracing, set Slow Request Standard, and click Save.

Configuring the Filtering Condition

1. Log in to FineOps as the admin and select the required O&M project. Choose Health Inspection > Template Performance.

2. Select Statistical Method.

• You can specify the calculation method for performance metrics including Loading Time, Number of Slow Requests, and Data Fetching Time.

• You can choose between Median (default selection) and Average.

3. (Optional) Tick Latest Version Only.

• If it is unticked, the system displays performance data of both the current and historical versions of the template.

• If it is ticked, the system displays performance data of the latest version of the template only.

4. Set the filtering condition.

Click Filter and configure the filtering condition. You can filter templates based on multiple dimensions. Click Search.

Viewing Overall Template Performance

All templates with slow performance that meet the filtering condition are displayed in a detail table.

The following table describes the detail table content.

Item	Description
Template Path	For a FineReport report, it refers to the full path of the template in the reportlet directory of the project. For a FineBI dashboard, it refers to the full path of the dashboard in the user's analysis.
Directory Name	It refers to the full path of the template in the mounting directory. If it is empty, the template is not stored in the mounting directory.
Number of Checks	It refers to the number of performance checks within the selected time range.
Loading Time	It refers to the average or median value of the first-page loading time. Note:  The first-page loading time refers to the time to load the visible content in a template for interaction after the template is opened. If multiple FineBI dashboards are opened simultaneously, the loading time of some dashboards may not be included in the summary calculation.
Number of Slow Requests	It refers to the number of requests with a response time exceeding the threshold defined in Slow Request Standard.
Data Fetching Time	The data fetching time of a single request (X) is defined as the total time spent fetching data from all datasets associated with the request. The data fetching time of a single access (Y) is defined as the average or median value of X across all requests during that access. The data fetching time of a template is defined as the average or median value of Y across all accesses of that template. Note: The data fetching time refers to the time spent fetching data using the extraction engine and direct connections, not including that for SQL queries without associated datasets. In scenarios involving parallel fetching or queries after first-page loading such as linkages, the total data fetching time may exceed the loading time.
Data Fetching Type	It refers to the data fetching type of FineBI dashboards only, including Data Extraction and Direct Connection.
Operation	You can click Template Detail to be redirected to the performance detail page of a specific template.

Viewing Single Template Performance

You can click the Template Detail button of a template on the overall template performance page to be redirected to the performance page of the template.

You can adjust the template while clicking the Refresh icon in the upper right corner to view the real-time effect.

The performance detail page of a single template consists of a distribution chart and a detail table.

1. Distribution chart:

• Each dot represents an access, allowing you to view the template loading time of each access.

• The dashed line in the chart indicates the average or median value of the template loading time.

2. Detail table:

Item	Description
Access Time	It refers to the time when the template is accessed.
Version Time	It refers to the version of the accessed template and the value is the last modification time of the template configuration.
Loading Time	It refers to the average or median value of the first-page loading time. Note: The first-page loading time refers to the time to load the visible content in a template for interaction after the template is opened. If multiple templates are opened simultaneously, the loading time may be skewed and is not referential.
Number of Slow Requests	It refers to the number of requests with a response time exceeding the threshold defined in Slow Request Standard.
Data Fetching Time	It refers to the average value of X (the total time spent fetching data from all datasets associated with a request) across all requests.
Data Fetching Type	It refers to the data fetching type of FineBI dashboards only, including Data Extraction and Direct Connection.
Data Volume	It refers to the maximum amount of data in a single fetch during this access. The returned value is the product of the number of resulting rows and columns.
Performance Risk	See the following table.
Operation	You can be redirected to the chain detail page to view the chain of requests at specific time. If the time is beyond the chain retention period, the chain details cannot be viewed. For details, see First-Page Chain and Call Chain.

The following table describes performance risks.