Metabase now gives you the ability to automatically cache the results of queries that take a long time to run.
To start caching your queries, head to the Settings section of the Admin Panel, and click on the Caching tab at the bottom of the side navigation. Then turn the caching toggle to Enabled.
End-users will see a timestamp on cached questions in the top right of the question detail page showing the time when that question was last updated (i.e., the time when the current result was cached). Clicking on the Refresh button on a question page will manually rerun the query and override the cached result with the new result.
In Metabase, rather than setting cache settings manually on a per-query basis, we give you two parameters to set to automatically cache the results of long queries: the minimum average query duration, and the cache TTL multiplier.
Your Metabase instance keeps track of the average query execution times of your queries, and it will cache the results of all saved questions with an average query execution time longer than the number you put in this box (in seconds).
Instead of setting an absolute number of minutes or seconds for a cached result to persist, Metabase lets you put in a multiplier to determine the cache's TTL. Each query's cache TTL is computed by multiplying its average execution time by the number you put in this box. So if you put in 10, a query that takes 5 seconds on average to execute will have its cache last for 50 seconds; and a query that takes 10 minutes will have a cached result lasting 100 minutes. This way, each query's cache is proportional to its execution time.
Lastly, you can set the maximum size of each question's cache in kilobytes, to prevent them from taking up too much space on your server.
If you need to use a map tile server other than the one Metabase provides, you can find more information on the next page.