I. Overview
During using Extracted Data Cache Introduction , if the user wants to know the usage of the cache, or wants to handle some abnormal caches manually, he or she can go to the Running Monitor interface in the Manage > Extracted Data Cachedirectory to learn about it.
II. Normal mode interface
The normal mode interface only displays some key information, which is mainly suitable for users to use the cache normally and observe the operation of the cache. As shown below:
Note: The user clicks the " Development Mode" button to enter the development mode interface.
1. Parameter panel
1) Parameter introduction
As shown in the table below:
Parameter | Instruction | Optional range |
---|---|---|
Template | Cache usage used to filter the specified template | All generated cached templates, empty query all |
Data Connection | Used to filter the cache usage corresponding to the specified data connection | All data connections that have generated a cache, if empty, query all |
Cache Status | Used to filter the cache usage of the corresponding cache mode |
Empty query all |
Sort by | Used to filter the cache usage of the cached result data volume (row*column) within the specified range | Empty query all |
Only display auto data extraction caches | When checked, only the automatic draw cache will be displayed | - |
2) Button introduction
Button name | Instruction |
---|---|
Disable All | After the click, all caches in memory will be invalidated, the cache history and rules will still be retained, and the cached content will be regenerated next time it is accessed |
Delete All | After clicking, all cache records will be cleared and initialized to a state where no cache is generated. At this time, the cache and cache records will be regenerated when the cached data set is accessed. |
Suspend/Restore Cache | Two buttons for pausing or resuming the cache respectively |
Development Mode | For details, please refer to Chapter III |
2. Overall overview
The description of each indicator in the overall overview is shown in the following table:
Index | Instruction |
---|---|
Overall Memory Usage | The current memory usage of the cache for the system |
Total Caches | The total number of caches generated so far (including expired caches) |
Eabled Caches | The current number of valid caches |
Auto Updates | The number of caches that are automatically updated according to the policy |
Overall Disk Usage | The current disk usage of the cache for the system |
3. List details
The meaning of each field in the table is shown in the following table:Field | Instruction |
---|---|
Id | Generate the UUID of the cached object, usually an id corresponds to a sql Click the cache id to hyperlink to the cache usage trend chart, showing the cache usage by timeline |
Template | The template that uses this cache object, if multiple templates are used, multiple sources are displayed |
Dataset | The name of the dataset used by the cache |
Data Connection | The name of the server data connection used by the cache |
Row | The amount of data to cache the result |
Column | |
Status | Cache state |
Hit/Trial | The number of attempts represents how many times the same sql in the cache is tried to be accessed, and the number of hits represents how many times the cache is used. Since the cache cannot be hit for the first time, the number of hits is at least 1 less than the number of caches. |
Update/add | How many times the cached data has been updated or added |
Expired | How many times the cached data has been invalidated |
Last Update | The last time the cached data was updated |
Elapsed Time | The fetch time corresponding to the last update |
Next Update | The estimated time of the next data update, if no automatic update will be performed, it will display no plan |
Cache Operation | Refresh : Immediately connect to the database to update, get the latest data from the specified cache Invalidation : After clicking, the specified cache will be invalidated, the cache history and rules will still be retained, and the cached content will be regenerated next time it is accessed Delete: After clicking, the specified cache record will be cleared, and the cache and cache record will be regenerated when the data set with the cache enabled subsequently is accessed. |
Click Next Update to view the current cached schedule details, as shown in the following figure:
The fields are described in the following table:
Field | Instruction |
---|---|
Use Global Config | Yes: Select Use Server Settingsfor cache settings No: Cache settings select Individually set for the template For details, please refer to: Section III.4 of Extracted Data Cache Introduction |
Termination Time | The time when the cache and its strategy are terminated. If the SQL contains some keywords that are not suitable for caching, the termination time will be set |
Whether Auto Adjusment | Indicates the update interval, whether automatic update will be automatically adjusted according to the access situation |
Idle time before termination | If the cache is not accessed for more than this time, it will be terminated (termination means clearing the cache, accessing data and policies), the default is 72 hours |
Update interval | Cache auto-update interval |
Last update time | The last update time of the cache |
Recent execution time | The time of the last fetch |
Continuously update failed time | The cumulative number of consecutive automatic update failures |
Last scheduled time | Refers to the check time of the last fetching task of the template by the scheduler Scheduling refers to the scheduler, and the scheduler checks all fetching tasks |
III. Development mode interface
This interface displays detailed information for admins or developers looking to learn more about the cache to assist in locating problems. As shown below:
Note: The introduction of some parameters and buttons has been explained in Chapter II of this document.
1. Parameter panel
1) Parameter introduction
As shown in the table below:
Parameter | Instruction | Optional range |
---|---|---|
Elapsed Time | Used to filter the cache usage of SQL time-consuming within the specified range | 0 or positive integer, empty query all |
Expected update time | Used to filter cache usage for upcoming data updates within a specified time frame | 0 or positive integer, empty query all |
Auto Only | Used to filter the usage of the cache that will be updated automatically. Automatic update: the cache that will be automatically updated will update its data regularly or at a fixed frequency, and it will remain valid continuously. The cache that is not automatically updated will be invalid after the expiration time | - |
Source | Template Access: Normal preview template generated cache Recommended prediction: enable the cache automatically generated by the "parameter prediction" function | - |
2) Button introduction
Output Jstack: Click this button to generate a Jstack, which is convenient for developers to troubleshoot when an exception occurs.
2. List Details
button name | instruction |
---|---|
View Energy Efficiency Values | The indicator used to evaluate the use of the opened cached template, the value is 0 to 1, the higher the performance, the better the use of the opened cached template After clicking, the interface is as shown below: |
View cache update trends | After clicking, the hyperlink shows the trend change of cache update, which is used to confirm the cache queuing pressure |
Cached template | Display the number of cached templates, click the hyperlink to display the specific cached templates and their detailed data After clicking, the interface is as shown below: |
View Performance Segments | Display the scores of various dimensions of performance to help confirm the reasons for the cache effect and the direction of improvement After clicking, the interface is as shown below: |
Scheduler monitoring | Click the hyperlink to view the operation of the cache scheduler |
View sql | After clicking, the hyperlink will display the sql corresponding to the cache |
View parameters | After clicking, the hyperlink will display the parameters corresponding to the cache. |