Thanks Kevin. I presumed it wasn't specifically tied to that, although when I did test the multi-monitor/window on our "offline" lab system, I noted every time the client started, I had an EDT event. It didn't continue like on site with other issues, which could make sense as I don't have the full array of PLCs connected and most of my data is bad at the moment.
Also look for tag() expression bindings. That can have a pretty negative affect as well. And as referenced above loads of readBlocking in loops.
This morning I reverted to a backup of our gateways which I took on October 3. The system has been running for almost 4 hours and it's performance has drastically improved. It's not where we want it to be, but it's usable.
So, now just trying to figure out what changes that were made during the week of 10/9 affected the performance so terribly.
Thank you to everyone that provided feedback and suggestions.
Please PLEASE report back how you fixed/improved the issue to help future users
4 Likes
I don't really consider the problem fixed. We've had slow performance since day 1, but the system has been usable. In an attempt to improve things, changes were made last week that resulted in very poor performance, but we can't figure out why. So, I've reset the system to a "last good state" just so we can operate.
Much work to be done to get the performance where I expect it to be.
You should be able to double click on that result in the search and it should just open the binding for you. I find it odd you searched for system.alarm.queryStatus specifically, the result showed that expression binding as a result, but system.alarm.queryStatus is no where to be found inside of it, I have to think there is somewhere, otherwise why is it listed as a result in the search bar here (unless its still in the expression, commented out).
1 Like
I'm sure you've seen these, but I wanted to stress that if the alarm components @jpark is talking about were always on your screen, I would recommend taking this suggestion seriously as I have seen this be an issue before. It is much easier to try this first than to hunt down scripts/expressions. This is only if you haven't already tried it...
Thanks for the feedback. Will definitely keep this in mind.
Sounds like poor programming or hardware. I have our server handling over 100,000 tags across 30 PLC's, 6 seperate projects, with over 30 clients running. Not one single thing lags.
1 Like
Or IA could recognize the issue and fix them on their own.