Gateway 8.3.4 (b2026030309)
Siemens Enhanced Driver 1.3.4 (b2026030309)
Connectivity:
Port: 102
Timeout: 30000 ms
Device:
Device Type: S7_1500
Address Type: SYMBOLIC
Rack: 0
Slot: 1
Advanced:
Optimize Writes: Enabled
Secure Connection Mode: PREFERRED
Password: None
Usually it is something simple like that causes issues, I'm logging again now to see what causes the memory to grow, and experiment later to see if I can get it to release the memory back.
What kind of memory is available on this machine? 16GB of heap seams like a lot for a "small" system. I have a plant wide system with over 300K tags, and am only allocating 8GB.
Allowing the JVM too much memory can also be an issue, particuarly when installed beside a memory hungry application like SQL.
Be sure that you are setting your ingition.conf settings so that the JVM allocates all of the memory it should use up front, that way it isn't having available memory stolen from it by other applications. The inital heap size should match the max allowance.
Some would change this to the above. Of all the OS's available for a single machine system like this, Windows is undoubtedly the worst option.
Yes it is much, it was a test to see what will happen to see if i increased it, 4GB should be plenty. I will change it back during the evening and make sure it is all allocated from start.
Server itself have 64 GB, the production server has 32.
SQL is capped in express, and even if we would use ms sql standard we would set the limit how much for it to use.
Databases, in general, have distinctly different RAM, CPU, and Disk workload behaviors. They do not play well with Ignition in the same system. At least separate them into VMs on a hypervisor, without overcommitting the resources.