How to reduce first transaction ClassLoader time after application restart?
We have a new Java service that takes extremely long time loading classes before doing anything in the first transaction after JVM started. We confirmed it using dynaTrace. Could you give us some suggestions on how to reduce this ClassLoader overhead? Thanks.
After application restarting, dynatrace agent will transfer classes to collector.
It will take resource. It will spend long time if more classes has been instrumented. For example: more sensor was defined.
It also related to the network speed between collector to agent.
We have this problem even without using dynaTrace. dynaTrace just helped us to confirm it.
My question is to get suggestion of general best practice to reduce first transaction response time.
There can be a number of different reasons why startup takes a long time, e.g. there may be a huge number of classes loaded as part of startup or accessing the jar-files during startup is slow, e.g. by having them on a network shared filesystem.
Maybe you can give some details and numbers about your environment, e.g. what type of application, is an application server involved, how many classes are loaded after startup is finished (visible in the Agent Overview Dashlet in dynaTrace), ...
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
