While performing peak-use-case testing, I was made aware that the embedded JVM for the IAMCS (aka JCS) was updated to x64. This interested me, since we now can increase the default memory from max of 1GB to X GB.
To determine if there was value in this process, I decided to update the MS Windows Registry (for the remote JCS/CCS) component, to both update the memory, JVM switches, and test with other JVM updates.
View of the im_jcs service with %CPU utilized while being stress tested.
View of the stress test results using dxsoak command:
= 60 updates/second.
View of the number of open threads to the im_jcs service during stress testing.
View of update to the memory settings (JvmMx = max memory), (JvmMs = initial memory), and update to the JVM Options; Remove the JDK7 switch (maxpermsize) and added com.sun.net.ssl.enableECC=true Cipher Suite update).
- During testing with external JVMs, update the "Jvm" setting to point to the correct jvm.dll file.
When testing with external JVM, update the Environment path to use this JDK first.
Interesting...thanks for sharing.