Our VM has 8 Cores, 16 GB RAM, and only kepware and Ignition on it. our SQL installation is located on a different VM. With no running clients or designers, and only kepware running, zulu is consistently running between 8-15% CPU usage. While kepware is running 15-20%
Huh. Sounds like you've subscribed to more PLC variables than you actually need. Or, perhaps, faster than you need. Did you drag and drop your entire PLC's tag tree from the OPC browser to the Ignition tag browser? (Hint: Don't do that.)
1 Like
well that is something I'm wondering. The kepware brings in Tag data from SEL plant controller (solar) but we currently don't have the connection made between kepware and the plant controller, only between kepware and Ignition. I've wondered if the data lack of connection is causing CPU issues, but in past projects we struggled with high CPU on this VM. not quite as consistently as I am seeing now.
A thread dump would be the first place I looked.
1 Like