How to profile Arclight performance?

[Berke Sokhan]

Hello all,

As the topic suggests, I want to run Arclight (but in a Docker container similar to the official https://hub.docker.com/r/dcm4che/dcm4chee-arc-psql) and profile its performance with some tool like VisualVM.

Did anyone manage to achieve this? 

Or in general how do you profile dcmchee-4arc-light (preferably while running in a Docker container)?    

Thanks for comments in advance.

Cheers,

- Berke

[Gunter Zeilinger]

You may adjust environment variable JAVA_OPTS and expose additional ports accordingly.

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[Berke Sokhan]

Thanks for the reply Gunter. I tried basic JMX properties but it didn't work with complaints about LogManager not being set. 

After some tinkering, I could manage to profile with VisualVM for a local running Arclight inside a Docker container specifying more JAVA_OPTS in docker-compose: 

        -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n

        -Dcom.sun.management.jmxremote.rmi.port=9797

        -Dcom.sun.management.jmxremote=true

        -Dcom.sun.management.jmxremote.port=9797

        -Dcom.sun.management.jmxremote.ssl=false

        -Dcom.sun.management.jmxremote.authenticate=false

        -Dcom.sun.management.jmxremote.local.only=false

        -Djava.rmi.server.hostname=localhost

        -Xbootclasspath/p:/opt/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar

        -Djboss.modules.system.pkgs=org.jboss.logmanager

        -Djava.util.logging.manager=org.jboss.logmanager.LogManager

So the extra D options (last 3 lines) are for specifying what log manager needs to be used and where can Wildfly find the log manager jar (it maybe in a different path for your version of Wildfly).

Cheers,

Berke Sokhan.

Gunter Zeilinger <gunt...@gmail.com>, 30 Oca 2019 Çar, 04:49 tarihinde şunu yazdı: