Issue
When opening a dashboard graphic, the system operates very slowly.
Navigation to other links with the Dashboard displayed, and clicking on a linked graphic does not display immediately.
Product Line
EcoStruxure Building Operation
Environment
- Building Operation 3.2.3 and higher
- Building Operation Automation Server Bundles (AS-B)
- Building Operation WebStation
Cause
Typically when a large number of stored values (100,000 per trend log) is needed to be displayed within the Dashboard widget (e.g., Period Chart) with a significant number of trend logs to be displayed (five or more) in the Dashboard, this will put excessive load on the AS-B and hence stops any or all navigation thereafter.
Dashboard widgets typically continue to read data required to be displayed after closing (or navigating away). This is to keep those logs cached for a few minutes after the dashboard is closed, so if the same logs are loaded again, then the data is available.
Any calculations are always done on the client, regardless of whether a chart, dashboard, or trend list is shown. The same is also true for WorkStation.
Resolution
Below are some considerations to look at improving the overall performance when dealing with this issue:
- Reducing the number of storage records from 100,000 to something more reasonable for the dashboard to display (5,000 - 8,000)
- Having these logs stored on the Enterprise Server and Dashboard operated from the Enterprise Server.
- If large storage is necessary, then create or use different logs for display within the Dashboards widgets.
- If the intention is always to show calculated values, use log processor trend logs. Log Processing Trend Log. These can be pre-calculated and thus contain only a fraction of the full source log's data amount.
- Upgrade to the later version (EBO 2023) as many optimizations have been made for Dashboards since 3.2.
