When a component in your report requests data, if that query matches a previously received query, then the new data request is served from the cache. The results of this query are cached for this particular scorecard.

The underlying query for the scorecard would be something like SELECT Sum(revenue) FROM (SELECT * from tableName)). Now, in your report, you add a scorecard with the metric Sum(revenue). The results of this query are not cached, since the cache applies to charts and components, not the data source as a whole. Let's say your data source connects to a custom SQL query: SELECT * FROM tableName. For example, the cache for a table with 2 dimensions and 3 metrics, having a default date range of the last 28 days, and filtered by some value (country = Belgium, for instance) will contain only the data needed to display that table. That cache contains only the data needed to create that component's default visualization.

How the cache worksĮvery component in a Looker Studio report has its own individual cache. Report editors can also manually refresh the cache (see below).

Refresh icon android studio