6.0
/
6.0.4
Moved BI Cache to the General tab.
6.1
Renamed BI Cache to Data Cache and moved Data Cache under the BI Parameter tab.
Log in to the FineBI system as the admin and choose System Management > System Setting > BI Parameter to set Direct Cache and Extraction Cache.
There are two options for Extraction Cache. After selection, click Save for the configuration to take effect immediately, as shown in the following figure.
The introduction to two global cache strategies is shown in the following table.
No Cache (Real-Time Query)
Send data requests to a data storage extracted from the project in each query.
Send data requests to a data storage extracted from the project whenever a query is made.
Use Extraction Cache
This policy is configured according to the cache survival interval. Whenever a cache is generated, it becomes invalid after the survival interval.
The cache is cleared every 24 hours by default.
The cache will be cleaned 24 hours after generation if you select this option.
Click Clear Cache At Once to immediately clear all caches related to SQL datasets of real-time data and DB database tables. All related queries will resend SQL statements to the database.
You can enable Dashboard Edit Acceleration. Click Save for the configuration to take effect immediately.
After enabling Dashboard Edit Acceleration, you can use the BI server to accelerate the query speed when part of the data in the dashboard is selected.
For all SQL datasets of real-time data and DB database tables, the global cache strategy takes effect on a data table if Follow Global Cache Strategy is set in the cache setting of the data table.
There are three options for Global Cache Strategy. After selection, click Save for the configuration to take effect immediately, as shown in the following figure.
The introduction to three global cache strategies is shown in the following table.
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 N Second Clear Cache Once
The cache is cleared every 600 seconds by default (recommended to keep). You are advised to set the range from 60 to 1800.
If the configured value is too small, the performance will be reduced when you access the same data repeatedly.
If the configured value is too big, the timeliness will be reduced when you access data.
300 seconds
After the 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 N (time) Clear Cache Once
Every Hour N (time) Clear Cache Once
This policy is configured according to the update time of the data source. No matter when the cache is generated, the cache expires at the configured expiration time.
You can set the cache to expire at a specific moment of each day. You can select multiple moments.
You can set the cache to expire at a specific minute of each hour. You can select multiple minutes.
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, the query results of all queries from 2021/9/18 8:00:00 to 2021/9/18 13:00:00 can be directly obtained.
When the first query is made after 2021/9/18 13:00:00, the cache expires. The query resends SQL statements to request data from the database. The query results of all queries from 2021/9/18 13:00:00 to 2021/9/19 8:00:00 can be directly obtained .
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy