Output Option Caching
Option outputs involve a large number of calculations and algorithms working on large numbers of connected data sets.
In order to view the outputs, many of the results must be cached for fast loading and querying.
Caching Levels
Caching is performed on two levels:
Results Caching: All of the costs and benefits will be calculated and saved in database tables. A change that requires new results, such as changing an impact dataset version, will put the option in an uncached state.
API Caching: Data-intensive API calls will be cached on the server for fast page-loading. Actions that invalidate the API cache may be able to clear the cache without setting the option to an uncached state. This may result in a slow loading page but it will be fast again on subsequent loads.
Option Caching
While an option is caching, it may display previous data. This data will be refreshed once caching is complete.
When an option is uncached, a pill will show on the option that states Cache Required. You can start the caching process by clicking the Start Cache button. During caching various option screens will not be available to interact with, such as the cost outputs.
While an option is caching, option editing functionality will be disabled, such as editing the Calendar or changing the Cost Data Set.
