Overview
Version
FineBI Version | Functional Change |
6.0 | / |
6.0.4 | Moved BI Cache to General. |
Functions
Log in to the FineBI system as the admin and choose System Management > System Setting > General to set Extract Cache and BI Direct Connect Cache Settings.
Extract Cache
There are two options for Extract Cache. After selection, click Save to take effect immediately.
The introduction to two global caching strategies is shown in the following table.
Note:
Global Cache Strategy | Introduction | Example |
No cache and real-time query | Send SQL statements to request data from a database in each query. | Send SQL statements to request data from a database whenever a query is made. |
Every Ns Clear one cache | Set according to cache survival intervals. Whenever a cache is generated, it becomes invalid after the survival interval. The cache is cleared every 600 seconds by default (recommend to keep). It is recommended to set in the range from 60 to 180. Low configuration will reduce the performance when you access the same data repeatedly. Extremely high Configuring will reduce the timeliness when you access data. | Set to 300 seconds. After cache is generated after the first query (2021/9/18 14:10:00), the cache will expire at 2021/9/18 14:15:00. The first query after 2021/9/18 14:15:00 will resend SQL statements to request data from the database. |
BI Direct Connect Cache Settings
Clear caches at once
Click Clear caches at once to immediately clear caches related to all SQL datasets of real-time data and DB database tables in the system. All related queries will resend SQL statements to the database.
Dashboard Edit Speed-up
You can enable Dashboard Edit Speed-up. Click Save to take effect immediately.
After Dashboard Edit Speed-up is enabled, the BI server is used to accelerate the query speed when part of data in the dashboard is ticked.
Memory Speed-up Engine
You can enable Memory Speed-up Engine. Click Save to take effect immediately.
After Memory Speed-up Engine is enabled, the BI server is used to accelerate the query speed when data volume is less than 100,000 rows in computation.
Global Cache Strategy
Effective Object
For all SQL datasets of real-time data and DB database tables, the Global Cache Strategy takes effect on the data table if Follow global cache strategy is set in the cache setting of the data table.
Cache Strategies
There are three options. After selection, click Save to take effect immediately.
The introduction to three global caching strategies is shown in the following table.
Note:Global Cache Strategy | Introduction | Example |
No cache and real-time query | Send SQL statements to request data from a database in each query. | Send SQL statements to request data from a database whenever a query is made. |
Every Ns Clear one cache | Set according to cache survival intervals. Whenever a cache is generated, it becomes invalid after the survival interval. The cache is cleared every 600 seconds by default (recommend to keep). It is recommended to set in the range from 60 to 180. Low configuration will reduce the performance when you access the same data repeatedly. Extremely high Configuring will reduce the timeliness when you access data. | Set to 300 seconds. After cache is generated after the first query (2021/9/18 14:10:00), the cache will expire at 2021/9/18 14:15:00. The first query after 2021/9/18 14:15:00 will resend SQL statements to request data from the database. |
Every Ns Clear One Cache Every Hour N (time) Clear One Cache | Set according to the update time of the data source. No matter when the cache is generated, it expires at the set expiration time. You can set the cache to expire at a specific moment (can select multiple moments) of each day. You can set the cache to expire at a specific moment (can select multiple moments) of each hour. | Set the cache to expire at 8:00:00 and 13:00:00 every day. After the cache is generated in the first query on 2021/9/18 8:00:00, all queries from 2021/9/18 8:00:00 to 2021/9/18 13:00:00 can directly obtain the results. When the first query is made after 2021/9/18 13:00:00, the cache expires. It sends SQL statements to request data from the database. All queries from 2021/9/18 13:00:00 to 2021/9/19 8:00:00 can directly obtain the query results. |
