The WebUI cache is used to improve the response time of the WebUI by storing and refreshing some data that requires complex calculations, such as the number of applicable devices or patches1.
The cache refresh interval, also known as the cache Time To Live (TTL) value, determines how often the cached data is invalidated and updated1. The default value is 600 seconds (10 minutes)1.
To change the cache refresh interval, you can use the client setting _WebUIAppEnv_CACHE_TTL and enter the desired interval in seconds1. The minimum value is 180 seconds (3 minutes)1.
Increasing the cache refresh interval can reduce the impact on system resources, especially for large deployments and intensive patching activities1. However, it can also affect the freshness of the cached data1.
Another setting that affects the WebUI caching is _WebUIAppEnv_CACHE_INTERVAL, which determines how often the WebUI checks for new data from the BigFix server1. The default value is 60 seconds1.
Decreasing the cache interval can improve the responsiveness of the WebUI, but it can also increase the load on the BigFix server1. Therefore, you should balance the cache interval and the cache TTL values according to your needs and environment1.
The other settings, _WebUIAppEnv_SP_QUEUE_CONCURRENT, _WebUIAppEnv_DATA_REFRESH_SECONDS, and _WebUIAppEnv_SITE_CACHE_SIZE, are not related to the WebUI cache refresh interval12.
_WebUIAppEnv_SP_QUEUE_CONCURRENT limits the number of stored procedures that run simultaneously per app in the background that update cache values1. The default value is 51.
_WebUIAppEnv_DATA_REFRESH_SECONDS determines how often the WebUI polls the BigFix server for new data2. The default value is 15 seconds2.
_WebUIAppEnv_SITE_CACHE_SIZE specifies the maximum size of the site cache in megabytes2. The default value is 100 MB2.
