How Composer Caches Data
Composer uses a visual cache to enhance performance in scenarios where large numbers of users are concurrently viewing the same shared visuals. A metadata cache is also used to store field statistics.
Cached data is shared between users only if they have the same data access permissions and security context.
When caching is enabled, Composer does not requery the data source to obtain the data unless the cache is cleared or unless a refresh schedule is defined in the data source configuration. See Refresh Tab and Trigger Refresh Jobs.
By default, data caching is enabled for all data sources. The Composer cache stores all the results of aggregated requests from your data source. When a visual is created the request is first sent to the Composer cache. If the required results are found in the data cache, they are applied to your visual.
If the required results are not found in the Composer data cache, the data flow is as follows:
The request is sent to the Composer cache.
When the required results are not found in the Composer data cache, the request is sent to the data source.
The results from the data source are sent to the Composer data cache and stored there.
The visual displays the requested data.
Review the following links to learn how you can control Composer data caching.
- Clear the Cache for a Data Source Configuration
- Disable Data Caching for a Data Source
- Trigger Refresh Jobs
You can force Composer to bypass the cache and to query the underlying data source by selecting Refresh All from a Composer dashboard menu.