The results of that new query are then added to the table's cache, and Data Studio remembers the new query for future use. For example, if a viewer changes the date range or filters the table described above by a new country, then Data Studio requests the new data from the underlying data set. If the request can't be served from the cache, Data Studio requests the data from the underlying data set. 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.
![aqua data studio increase memory aqua data studio increase memory](https://cdn.shopify.com/s/files/1/1409/9796/products/pro2015_15512gb__apple_macbook_pro_2015_15_retina_i7_16gb_512gb_1553596651_13d1738d0_1024x1024.jpg)
![aqua data studio increase memory aqua data studio increase memory](http://italiaoperf.weebly.com/uploads/1/2/7/6/127679395/487409636_orig.jpg)
That cache contains only the data needed to create that component's default visualization. How the cache worksĮvery component in a Data Studio report has its own individual cache. Report editors can also manually refresh the cache (see below).