Caching
Dashboard instance caching mechanism ensures two important performance advantages:
Once a hidden and cached dashboard is displayed again, its startup bindings are not re-evaluated
Cached dashboards keep user input (e.g. values in text fields) that were not yet transferred to server's "main" data model
Caching can be enabled for all dashboards (via Web UI plugin settings) or individual dashboards only (via dashboard settings).
Caching configuration allows to limit cache size to a specific number of dashboard instance IDs or by maximum amount of RAM consumed by all dashboards. Once a cache size limit is reached, the oldest dashboard instances will be shut down and their next displaying to the user will cause their complete restart (including startup binding execution, etc.)
See dashboard lifecycle section for more information on how caching affects dashboard behaviour.
 | Dashboard Caching can only be applied to Iotellect Server web applications that are encrypted with an SSL certificate. Install an SSL certificate if you plan to enable caching for one or more dashboards. |
Was this page helpful?