High CPU Usage - Diagnosing

[pturmel]

@oscar.salcedo

I have attached a copy of our ignition.conf file

You have both CMS and G1GC set in your ignition.conf. G1GC is last, so that was chosen, but I recall reading that CMS settings can interfere with G1GC. Get rid of the wrapper.java.additional.1, .2, and .3. Add a target pause time. Consider logging garbage collector performance to determine if that is the cause of your clock drift warnings. See these topics:

Gateway / Java question 7.7.2

I have a general question about the performance of the gateway. As a background, we’ve had Ignition for a few years and have upgraded our server a couple of times as the number of clients we have has grown (using in-house MES application). We were on a 32 bit version with a couple of CPUs and 4gb of ram. As we continued expanding use of Ignition, the CPU usage gradually bumped up to where it was hovering in the 70% range with occasional spikes. We switched to a 64bit/Windows Server 2012 with…

Migrating to Java G1GC garbage collection

Reading up on G1GC in forum posts, I’ve gathered: Clients Add jvm-args="-XX:+UseG1GC" to the end of the target string in the native client launcher shortcuts to use G1GC under Java 7 (from this post by @pturmel). On the other hand, I’m thinking this is not required as long as clients are running on Java 8+. See next point. Consider limiting Java versions to 8+ in gateway settings as G1GC is the default in Java 8 per this post by @pturmell. Also note G1GC is not fully supported prior to JDK7 r…