One of my previous customer has ignition (dont remember whih version), where they have to restart the server with ignition on because the server it self becomes slow (vm warer:ed server. They have alotted 8GB of ram and with weeks of logging the ignition never goes above 900MB of ram usage.
When the server slows down, they start to get production stop.
I know that ignition has the “recipy” part of the plc work data, the flow is:
PLC sends a type to ignition, this tag has an on trigger with script, that looks thru entered recipes in ingition.
Ignition takes the data for this part type, from a local MSSQL Datavase and put it into designated datablock in the plc, then sets a flag recipe is loaded and done.
PLC does work
ATM i dont have access to the project but wonder what i should start to look at, it does not sound like memory leak since the memory usage is stable over weeks, except the server slows down.
I am not sure, if a scheduler to reboot the gateway would solve this (bandaid for a broken leg), or what best approach would be.