1. Allowed selecting Median as the statistical method for performance data to reduce the impact of abnormal data.
2. Added a distribution chart on the individual template performance page to help you quickly understand the loading time of the template during each access.
3. Optimized field names in the detail table for better understanding.
The FineReport Template Performance function is one of the business performance monitoring capabilities provided by FineOps.
It helps you fully understand the resource access, time distribution, and performance trends of FineReport templates, so you can proactively identify and resolve performance bottlenecks.
1. Check the function scope.
This function applies only to templates accessed from desktops.
2. Ensure Tracing has been enabled.
Before using this function, make sure link tracing has been enabled. For details, see Prerequisites for Using Tracing.
3. Ensure Performance Setting has been configured.
Log in to FineOps as the admin, select the target project, choose Health Inspection > Business Performance, and click Performance Setting in the upper-right corner.
Click FineReport Template Performance, set Slow Request Threshold, and click Save to complete the configuration.
1. Log in to FineOps as the admin, select the target project, and choose Health Inspection > Business Performance.
2. On the Business Performance page, select FineReport Template Performance from the drop-down list to switch to the corresponding monitoring module.
1. Set Statistical Method.
You can specify the calculation method for performance metrics, including First Meaningful Paint, Slow Request Count, and Data Fetching Time.
You can choose between Median (default value) and Average.
2. Filter templates.
Click Filter and configure filtering conditions to filter the FineReport templates in the detail table.
Filters templates by access time range.
The start time defaults to five days before the current time.
The end time defaults to six hours after the current time.
All templates are selected by default. Multi-selection is supported.
You can select any template in the chosen mounting status.
Filters templates by average FMP.
It is empty by default and accepts positive integers.
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.
All templates with slow performance that meet the filtering condition are displayed in a detail table.
The following table describes the detail table content.
Full path of the template in the reportlet directory of the project
Full path of the template in the mounting directory If it is empty, the template is not mounted to the platform.
Average or median value of FMP time
FMP refers to the time from when a template is opened to when its visible content finishes loading and becomes interactive.
Number of requests with a response time exceeding the threshold defined in Slow Request Threshold
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.
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.
After adjusting the template, click 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:
Template version upon access and the time when the template configuration was last modified
If multiple templates are opened simultaneously, the time may be skewed and is not representative.
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.
Click Trace to go to the trace detail page and view request traces.
If the time is beyond the trace retention period, the trace details cannot be viewed.
For details, see First-Screen Trace and Trace.
The following table describes performance risks.
The network transmission takes a long time.
The DNS resolution takes a long time.
Fetching data from the dataset is slow.
Longer than 3 s
The volume of data fetched by a widget is large.
The data volume is greater than 10,000.
The cell sorting calculation takes a long time.
The cell conditional attribute calculation takes a long time.
The cell display calculation takes a long time.
The cell expansion calculation happens too many times.
The collapsible tree construction takes a long time.
The chart formula calculation takes a long time.
The data extraction is slow.
The data fetching based on direct connections is slow.
The permission query takes a long time.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy