How Zoomdata Caches Data
Zoomdata uses different caching methods for the different types of data that it works with:
- For aggregated result sets, Zoomdata leverages Spark to cache aggregated result sets.
- For streaming data, the information is cached and persisted in PostgreSQL.
- Introduced in Zoomdata 2.6.5, a new Visualization Cache was introduced to further enhance performance in large number of dashboard viewer scenarios.
Data Flow with Zoomdata Resultset Caching Enabled
Zoomdata Cache stores all the results of aggregated requests from your data source. In this scenario, when a chart is created the request is first sent to Zoomdata Cache. If the required results are found there, they are visualized on your chart.
Otherwise, the data flow is as follows:
- The request is sent to Zoomdata Cache.
- If the required results are not found in Zoomdata Cache, the request is sent to your data source.
- From your data source the results are sent to Zoomdata Cache and stored there.
- The chart displays the requested data.
For additional information about how Zoomdata implements Spark, refer to the article How Zoomdata Uses Apache Spark .
DISABLING Zoomdata RESULT SET CACHING
Zoomdata result set cache is a temporary storage of the aggregated data from your data sources. By default, caching is enabled for all data sources. However, you can disable it if your data source is constantly being updated, or you do not want to allocate the required RAM, or performance of your data source is high, so you do not need to store the aggregated queries.
Was this topic helpful?