(Appendix) Cache
Additional information for cache.
Last updated
Was this helpful?
Additional information for cache.
Last updated
Was this helpful?
In various scenes, we create and utilize caches with each query execution to prevent redundant background jobs.
This helps in reducing the amount of data scanned and in obtaining execution results faster.
If the SQL statement does not change, the warehouse-side cache (e.g., ) is used. When using SQL Chain, intermediate SQL results are automatically rewritten to use the cache table (it is also possible to disable the cache with an option).
SQL results of up to 1000 rows are stored within the Notebook or Report. Charts and other components can utilize these results up to 1000 rows (it is also possible to enable/disable this with an option).
If the same SQL is executed again within 24 hours, the saved display-ready data is retrieved and shown without running a new job.