In Strategy Intelligence Server environments, having a large number of caches (approaching the limit of 100,000 caches per project) may have an adverse effect on Strategy Intelligence Server startup time.
Loading the cache pool and cache lookup index tables
When Strategy Intelligence Server starts up, it must load the entire cache lookup index into memory. This does not necessarily include cache data, only information about the caches' location, status, and how the caches should match incoming report requests. This time is negligible for a modest number of caches, but the loading time increases roughly linearly with the number of caches.
It is not possible to circumvent loading the cache pool and cache lookup tables. Strategy administrators should evaluate the optimal trade-off between Strategy Intelligence Server startup time and the number of caches that will be allowed. In large deployments with thousands of users, where each user is allowed a relatively large number of history list messages (50 or more), it should be expected that starting Strategy Intelligence Server will be more time-consuming. To improve startup performance, it may be necessary to reduce the number of caches allowed per project and the number of history list messages per user.
Loading caches at startup
If a project is configured to load caches at startup, as shown in the image below, Strategy Intelligence Server will also load cache data for as many caches as will fit in the project's maximum cache RAM setting, in most-recently-used order. The time taken to load the caches' data is in addition to the amount of time required to load the cache pool and lookup tables.
Note: All types of report caches (Matching caches, Matching, History caches and History only caches) are loaded at startup.
Loading caches at startup improves performance at the first access of a cache that is preloaded. This can be less useful with a large number of caches because the more caches exist for the project, the less likely it is that a given cache will be loaded at startup. As the probability of preloading a specific cache decreases, the usefulness of preloading decreases also, and the performance impact of preloading the caches becomes less beneficial.
Strategy Intelligence Server startup time may be improved by disabling cache loading at startup. Disabling the setting will not cause the cache indices not to be loaded at startup.
