I’m currently working on evaluating the feasibility of adding a new project to an existing Ignition Gateway that is already running multiple projects. To ensure system stability and performance, I’d like to determine how much process load this new project might introduce and whether the Gateway has sufficient resources to handle it.
Does anyone have recommendations or best practices for assessing the load a new project might impose on the Gateway? Specifically:
Are there any tools or diagnostic reports within Ignition that can help forecast potential performance impacts?
What metrics should I focus on to estimate the Gateway's current capacity and headroom (e.g., CPU, memory, thread utilization)?
Have you found any guidelines or methods for predicting the additional load from scripting, tag updates, or client sessions?
Any insights, experiences, or resources you can share would be greatly appreciated!
I realize my initial explanation might not have been very precise, so I will try to clarify my question. I need to analyze which specific parts of the current solution are consuming the most system resources in order to identify areas for optimization.
While the number of sessions is certainly a relevant metric, I am looking for more detailed insights. Specifically, I would like to pinpoint elements such as device connections, screens, scripts, or any other components that are imposing a significant load on the system. This would allow me to focus on optimizing the areas that have the greatest impact.
Any guidance, tools, or best practices for achieving this level of analysis would be greatly appreciated.