Performance Tracking

1. Overview

Performance tracking is a real-time platform performance data monitoring and tracking function provided by Guandata, which can help users timely track current dashboard performance. By recording key indicators such as dashboard loading speed and card data calculation time, it can help users self-troubleshoot and locate performance issues.

For example, when dashboard loading is too slow, users can consider optimizing dashboard card design or data sources to improve performance.

Note:
1. Only V5.1.0 and above versions provide "Performance Tracking" function.
2. Currently, performance tracking data is not recorded in the database and is only for users to analyze real-time performance issues. If there are future iterations, updates will be released promptly.

2. Usage Guide

2.1. Enable Performance Tracking

The performance tracking entry is located in "More" in the upper right corner of the dashboard. To use this function, please contact Guandata staff in advance to enable it for you.

2.2. Performance Tracking Interpretation

Click "Performance Tracking", and the right side will display all card task time consumption during the current page loading process (only showing currently loaded cards on the current page, not including historical records). When scrolling down the page, it will continuously display the loading situation of rendered cards. For convenient report viewing, click the wide screen button to the right of "Performance Tracking" to set the display area to wide format.

As shown in the figure above, the upper part shows Gantt chart display, and the lower part shows table display.

When the page refreshes, it will record the page switch status of link performance. If not closed, after refresh, the current loading link performance will be appended below by default.

Currently displayed performance data mainly includes: dashboard card traceId, key time data during dashboard card loading process, etc.

The noun explanations involved in the performance tracking list are as follows:

Name	Explanation
First Calculation	The process of reading data from database/spark according to the card's SQL statement
Second Calculation	The process of performing advanced calculations (such as year-over-year, percentage, subtotals and totals) based on first calculation results
Cache Hit Status	Miss: Both first and second calculations miss First Hit: Represents first calculation hit, including cards with only first calculation, and cards with second calculation but miss, both display as first hit Full Hit: Represents both first and second calculations hit
serverWaiting	Time from receiving frontend request to starting data reading
pgWaiting	Time from starting data reading to waiting for writing to pg database
driverRunning	Time converted to physical engine
sparkRunning	Actual spark calculation time
cpuTime	CPU usage time
dbTime	Direct database query time
Data Transformation	Time to convert first/second calculation results to frontend required format

To further troubleshoot issues, users can take screenshots or report the traceId to operations personnel, who can then further view detailed operations logs to complete problem location and handling.