Store and purge data
The cache can retain up to 0.5 GB of reporting data and if it reaches capacity, it frees up space for new reports by purging the data for the least frequently used reports. You can change the retention value by revising the portal.properties parameter: portal.reports.cache.maxSizeInMemory.
See Configuring the maximum cache size in memory.
Purging also occurs when:
Portal Tomcat service is stopped
A cached report is more than 24 hours old
You can change the time period by revising the port.properties parameter: portal.reports.cache.timeOut.
See Configuring the cache time for reports.
The cache can be stored in memory. By default, it is located in:
Linux:
/opt/tomcat/aptare_instances/portal/temp
Windows:
C:\opt\tomcat\temp
Optimistic caching is used to pre-generate reports related to Inventory objects a user may not have selected. For example, if you select a category in the Inventory with 12 VM Servers, and choose the first VM Server, the next nine servers displayed in the Hierarchy Panel are queued up to have their inventory reports run and populated in the cache. This enables a quick return of reports and almost instant results.
Note, optimistic caching is designed to limit the load to the CPU of the Portal server. This means, that in the case of a large number of objects with a large number of associated reports, the caching speed is throttled down.
The mechanism can be fine tuned using guidelines provided by Cohesity Support.