Intro to Caching in ThirdEye

By default, ThirdEye uses an in-memory cache to reduce the number of fetch requests it needs to make to the data source. The in-memory cache is set to use no more than 1/3 of the JVM’s available memory, and can be disabled completely by setting “useInMemoryCache” to be “false” in cache-config.yml. See cache-config.yml. The code for the in-memory cache can be found in:

org.apache.pinot.thirdeye.detection.DefaultDataProvider

ThirdEye also provides optional support for using an external, centralized cache, either as a standalone cache or as an L2 cache. Currently, ThirdEye comes with a connector for using Couchbase as a centralized cache right out of the box. Details for this connector can be found in Couchbase as a Centralized Cache.

If you’d like to use a different data store for your centralized cache instead, see Setting Up Custom Centralized Cache.