JVM tunning for wildfly 22.0.0.Final

[Mohammed Alam]

Dear Team,

Please help us with JVM and thread tuning parameters for 8 instance on wildfly wildfly 22.0.0.Final each host is having 4 instance. Kindly help  us we have to go live on production

server resources-

- RAM-80

-CPU

Architecture:          x86_64

CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                32
On-line CPU(s) list:   0-31
Thread(s) per core:    2
Core(s) per socket:    8

Current configuration for each instance:

Domain.xml-

----------------------------------------------

<server-groups>
        <server-group name="eris-server-group" profile="full-ha">
            <jvm name="default">
                <heap size="1024m" max-size="4048m"/>
            </jvm>
            <socket-binding-group ref="full-ha-sockets"/>
            <deployments>
                <deployment name="jolokia.war" runtime-name="jolokia.war"/>
                <deployment name="blutoservice.war" runtime-name="blutoservice.war" enabled="false"/>
            </deployments>
        </server-group>
    </server-groups>

----------------------------------------------------------------------

HOST.XML

<jvms>
        <jvm name="default">
            <heap size="1024m" max-size="8096m"/>
            <jvm-options>
                <option value="-server"/>
                <option value="-XX:MetaspaceSize=2048m"/>
                <option value="-XX:MaxMetaspaceSize=2048m"/>
                <option value="-XX:ReservedCodeCacheSize=1024m"/>
                <option value="-XX:ParallelGCThreads=8"/>
                <option value="-XX:NewRatio=3"/>
                <option value="-XX:+UseParallelGC"/>
                <option value="-XX:SurvivorRatio=6"/>
                <option value="-XX:+UseLargePages"/>
                <option value="-XX:+AggressiveOpts"/>
                <option value="-XX:+UseFastAccessorMethods"/>
                <option value="-XX:+OptimizeStringConcat"/>
                <option value="-XX:CompileThreshold=500"/>
                <option value="-XX:PermSize=512M"/>
                <option value="-XX:MaxPermSize=512M"/>
                <option value="-XX:NewSize=820M"/>
                <option value="-XX:MaxNewSize=820M"/>
                <option value="-DENV=prod"/>
            </jvm-options>
        </jvm>
    </jvms>

 <servers>
        <server name="server-1" group="eris-server-group" auto-start="true">
            <jvm name="jvm-rpa1">
                <jvm-options>
                    <option value="-verbose:gc"/>
                    <option value="-Xloggc:/opt/wildfly22/domain/servers/server-1/log/gc.log"/>
                    <option value="-XX:+PrintGCDateStamps"/>
                    <option value="-XX:+UseGCLogFileRotation"/>
                    <option value="-XX:NumberOfGCLogFiles=5"/>
                    <option value="-XX:GCLogFileSize=3M"/>
                    <option value="-XX:-TraceClassUnloading"/>
                    <option value="-XX:HeapDumpPath=/opt/wildfly22/domain/servers/server-1/log"/>
                    <option value="-XX:+HeapDumpOnOutOfMemoryError"/>
                    <option value="-XX:+PrintGCDetails"/>
                </jvm-options>
                </jvm>
            <socket-bindings port-offset="200"/>
        <system-properties>
            <property name="eris.node" value="1" boot-time="true"/>
        </system-properties>
        </server>

[James Perkins]

This is not something that can be done generically. It depends on a lot of different factors.