JIT-Compilation
The JIT-compilation view helps to identify scenario start-up delays caused by unwanted JIT compilations.
JIT compiled modules cannot be shared among processes. This leads to increased CPU usage, higher memory pressure and increased loading times compared to shared based native images which are “loaded” in no time.
For each module the following information is provided:
Column Name |
Description |
Module Name |
Name of the module/assembly |
Module Path |
Complete path of the module |
Image Size [Bytes] |
Total size of the mapped image (module) in bytes |
Σ JIT Time [ms] |
Total elapsed clock time [in ms] to JIT compile methods for all JIT compilations in the specified module during scenario execution |
Σ CPU JIT Time [ms] |
Total CPU time [in ms] spent to JIT compile methods for all JIT compilations in the specified module during scenario execution |
# JIT Compile |
Number of JIT compile operations that occurred during the scenario execution in the specified module |
Σ IL Size [Bytes] |
Total size of the IL code that was compiled including all JIT compilations in the specified module during scenario execution |
Σ Native Size [Bytes] |
Total size of the jitted code that was generated in all JIT compilations for the specified module during scenario execution |
Coverage [%] |
Σ IL Size [bytes] / Image Size [bytes]:The ratio of the compiled IL code to the size of the module indicates how much of the code was already compiled during scenario execution |
Trigger Call Stacks |
Call stack which triggered the operation |
In order to investigate the triggers call stacks for JIT compilations view the JIT-Compilation -Trigger Stack: