I am using several instances of the trend widget on a single page of my WebIQ application, alongside the Trend Select widget, and I'm experiencing a lot of lag and instability from the widget when I'm trying to make interact with the widgets from the UI.
Here is a description of my overall setup:
I've installed the WebIQ Runtime on a Windows Server 2025 Standard PC, and am accessing it via a web browser on this same PC. The processor is an Intel(R) Xeon(R) E E-2488 3.19 GHz, and it has 32GB of DRAM.
I have a single data recorder that's capturing 1,560 bytes of data every second from an OPC UA server running on a ctrlX CORE. Inside of the Recorder Manager, I've defined 13 different trend groups, and partitioned the data evenly (i.e. each trend group is growing by 120 bytes/s).
The default timespan for the Trend object is 12 hours.
On a single page of my WebIQ visualization, I've created 13 Trend objects, and mapped each one to a separate Trend Group. Based on navigation buttons at the top of my UI, I am selectively showing one of these Trend objects at a time (and hiding the remaining 12 objects).
Each Trend object also has an associated Trend Select widget to its left. I am using this to allow operators to select the data from the Trend Group that should be displayed.
I'm attaching a video that shows the problematic behavior that I'm experiencing. Here is a general description of the symptoms:
The trend system is generally very sluggish when trying to do any kind of update through the UI.
The main time this manifests is when selecting / deselecting the checkboxes from the left pane. When checking a new box, the hourglass often spins indefinitely.
Sometimes toggling other boxes causes it to complete its operation.
Sometimes after checking a box the trend appears in the main view on the right, but the color icon in the left navigation menu is missing.
And occasionally the main trend disappears altogether during loading.
Overall, this instability is making the Trend widget unusable at the moment. Do you have any suggestions for how to remedy this problem? I'm also interested in any feedback on the architecture, and any concerns you would have about the volume of data we're working with (i.e. is the WebIQ Trend widget designed to work with this quantity of data?).