Amazon Redshift Introduces Result Caching for Sub-Second Response for Repeat Queries
Amazon Redshift improves performance for repeat queries by caching the result and returning the cached result when queries are re-run.
Dashboard, visualization, and business intelligence (BI) tools that execute repeat queries will see a significant boost in performance due to result caching. In addition, result caching frees up resources to improve performance of all other queries.
When a query executes, Amazon Redshift searches the cache to see if there is a cached result from a prior run. If a cached result is found and the data has not changed, the cached result is returned immediately instead of re-running the query. If no cached result is available or if data has changed, the query is re-run and the new result is cached for future runs. When the cached result is returned, processing resources are conserved and made available for other queries.
With this release, we added a new ‘source_query’ column to the SVL_QLOG view that shows if a query uses result caching. Result caching is enabled by default on all Amazon Redshift clusters. To learn more, visit our documentation.
With the latest release, Amazon Redshift customers will have Result Caching in all AWS Public Regions.