Hi All,
Can someone explain why we have high CPU and Memory usage on our IGNITION Scada?
Is there a way to find out why and how it is happening?
Is this on a Virtual Server Instance?
Yes it is.
You have something odd happening, every ~10 seconds your internal OS clock registers a drift of over a second. It is something I would expect from a server that is heavily loaded by other VMs and they are stealing a lot of the resources.
We found an issue now:
is there are better way to do polling dataset tag history as we monitoring amps of the drives to see any changes for fault finding?
Why does this need to update every second? The final dataset ends up only showing the minimum value for each ~28 second block of history, you would be better off updating every 30 seconds.
We have no idea what that metric is telling us, it could be literally any script on your gateway.
It is only my project causing this. If I disable it it goes back to normal.
Is there better way to find out what causing this exactly?
Any logs?
What scripts are you running in the project?
This one to set the alarm
That looks like a pretty normal memory chart. And a relatively light CPU load. My gut says nothing is wrong.
It was running polling every second on session start and as more perspective sessions are open CPU utilization went over the roof. Thanks, we did figure it out.
This forum is a place to get help and share solutions. Care to share what you figured out?
6 Likes
I would like to mention something here, as it seems there may be some frustration about not knowing what is happening, which I completely understand. However, I would not want you to have the impression that Ignition lacks diagnostic tools.
Technically, Ignition was executing what you or the system designer programmed. While the values may appear “high,” they are not necessarily high from the system’s perspective. Ignition will use the resources required to execute the tasks that were designed.
Because of that, there would be no reason to expect log entries for every normal system activity.
If the polling rates were intentionally designed/configured to run every second, then the hardware simply needs additional resources to support that load or revise the infrastructure. If those polling rates were not intended to run at that frequency, then the issue would be a design/programming problem rather than a system/Ignition issue.
1 Like