Hi Nick,
We had an alarm status table on a bottom dock. Removing it made made a huge improvement. We now use a gateway script using system.alarm.queryStatus() that periodically writes to a tag. We then have a standard table that shows the alarms form that tag. This was the advice from iControls and Inductive Automation support. After implementing, thread counts have not increased out of control. Hopefully, the new alarm status table coming September/November 2021 will be good enough to put back.
Furthermore, some of our templates had some scripts that had blocking functions. Although they didn’t seem to have as big of an issue as the alarm status table on the bottom dock but writing them more efficiently made it system render pages quicker and reduce thread counts. Just thought I should mention it.
Lastly, we have increased our hardware and memory.
As can be seen in the image below, our thread count only reached a max of around 5,000. This may have been when we did stress testing. In any case, much less than the 20,000 plus threads then before. We sometimes have over 20 concurrent users of our project.
