# Front end performance is dismal

**URL:** <https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [October 13, 2023, 8:19pm UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474 "2023-10-13T20:19:50Z")\
**Posts on this page:** 10\
**Page:** 3

<div class="post-metadata">

**Author:** ![dbailey](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dbailey/32/77633_2.png) [@dbailey](https://forum.inductiveautomation.com/u/dbailey)\
**Post date:** [October 18, 2023, 2:45am UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/42 "2023-10-18T02:45:25Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\
**Post date:** [October 18, 2023, 8:29am UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/43 "2023-10-18T08:29:54Z")

</div>

Also look for tag() expression bindings. That can have a pretty negative affect as well. And as referenced above loads of readBlocking in loops.

---

<div class="post-metadata">

**Author:** ![Travis\_Graham](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/travis_graham/32/53480_2.png) [@Travis\_Graham](https://forum.inductiveautomation.com/u/Travis_Graham)\
**Post date:** [October 18, 2023, 4:33pm UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/44 "2023-10-18T16:33:26Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\
**Post date:** [October 18, 2023, 4:45pm UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/45 "2023-10-18T16:45:19Z")

</div>

Please PLEASE report back how you fixed/improved the issue to help future users

---

<div class="post-metadata">

**Author:** ![Travis\_Graham](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/travis_graham/32/53480_2.png) [@Travis\_Graham](https://forum.inductiveautomation.com/u/Travis_Graham)\
**Post date:** [October 18, 2023, 4:52pm UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/46 "2023-10-18T16:52:38Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [October 18, 2023, 5:00pm UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/47 "2023-10-18T17:00:25Z")

</div>

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).

---

<div class="post-metadata">

**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\
**Post date:** [October 18, 2023, 5:12pm UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/48 "2023-10-18T17:12:42Z")

</div>

> [@jpark](#):
>
> Are you using any of the red alarm label components on the header?

> [@jpark](#):
>
> It's always that alarm button that people put on a header.

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...

---

<div class="post-metadata">

**Author:** ![Travis\_Graham](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/travis_graham/32/53480_2.png) [@Travis\_Graham](https://forum.inductiveautomation.com/u/Travis_Graham)\
**Post date:** [October 18, 2023, 5:49pm UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/49 "2023-10-18T17:49:43Z")

</div>

Thanks for the feedback. Will definitely keep this in mind.

---

<div class="post-metadata">

**Author:** ![Matthew\_Emburgh](https://avatars.discourse-cdn.com/v4/letter/m/e5b9ba/32.png) [@Matthew\_Emburgh](https://forum.inductiveautomation.com/u/Matthew_Emburgh)\
**Post date:** [October 19, 2023, 9:22pm UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/50 "2023-10-19T21:22:24Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Dustin\_VanKeuren](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Dustin\_VanKeuren](https://forum.inductiveautomation.com/u/Dustin_VanKeuren)\
**Post date:** [September 28, 2024, 2:16pm UTC](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474/51 "2024-09-28T14:16:18Z")

</div>

Or IA could recognize the issue and fix them on their own.

[Previous page](https://forum.inductiveautomation.com/t/front-end-performance-is-dismal/80474.md?page=2)
