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.
Wipe Windows off the bare metal system and put any modern Linux there. Install virt-manager and quemu-kvm. Divvy up the resources to two VMs, with a some kept back for the host (to run the client GUI). Install DB in one VM, Gateway in the other.
This reminds me of another scada platform which shan't be named, where to install the scada software you have to install the rest of the universe as well
I remember last time it took maybe 2-3 hrs just to install everything. Maybe my brain is exaggerating since it's been many years now, but it was a long time regardless. It was the difference between 3D printing with a 0.2mm nozzle at 0.04mm layer height compared to a 0.4mm nozzle at 0.2mm layer heights (guess who recently bought a 3D printer )
I'm having flashbacks...
I'm recalling a certain DCS system that was easily much longer, likely measured in days. If you don't follow their several-hundred-page installation manual to-a-T, per station, you'll likely be rejected by ongoing support.
Just try it. I recommend using an X11 based desktop (not Wayland) for best compatibility with VMs (particularly for clipboard integration) and for best NVidia support.
I currently use Debian 12 (Bookworm) with X11 & KDE on my workstation. I'll be moving to Debian 13 (Trixie) shortly.
Linux Mint - super easy to use. Mostly all the posts you find for ubuntu apply, but without the overhead of ubuntu. Based on Debian way down deep, so most of what Phil tells you will also apply.
We've been having good results using Debian. We did one system with Ubuntu at the customer's request and it went generally smoothly.
Ignition on Linux is quickly becoming my preferred configuration even though I have to lean heavily on my team to do the Linux configuration currently. It runs so well.