RFR: 8356027: Print enhanced compilation timings [v2]
Ashutosh Mehra
asmehra at openjdk.org
Fri May 2 16:30:50 UTC 2025
On Thu, 1 May 2025 19:19:32 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:
>> In Leyden, we have the extended compilation timings printouts with -XX:+PrintCompilation / UL, that are very useful to study compiler dynamics. These timings include:
>> 1. Time spent before queuing: shows the compilation queue bottlenecks
>> 2. Time spent in the queue: shows delays caused by queue bottlenecks and compiler load
>> 3. Time spent actually compiling: shows the per-method compilation costs
>>
>> We should consider the same kind of printout for mainline. This would also require us to print the compilation task _after_ the compilation, not only before it. This improvement would also obviate any need for `PrintCompilation2` flag, [JDK-8356028](https://bugs.openjdk.org/browse/JDK-8356028).
>>
>> The difference from the output format we ship in Leyden:
>> 1. This output prints before/after the compilation to maintain old behavior partially. The "before" printout is now prepended with `started` to clearly mark it as such.
>> 2. The output is raw number in microseconds. In Leyden repo, we have these prepended with characters, like `C0.1`, but that prepending makes it a bit inconvenient with scripts. This PR also does microseconds, instead of fractional milliseconds. This should be enough to capture the wide range of durations.
>>
>> See the sample `-XX:+PrintCompilation` output in the comments.
>>
>> Additional testing:
>> - [x] Linux x86_64 server fastdebug, `compiler`
>> - [ ] Linux x86_64 server fastdebug, `all`
>
> Aleksey Shipilev has updated the pull request incrementally with one additional commit since the last revision:
>
> Test TestDuplicatedLateInliningOutput.java
While you are refactoring this, if you can also add a title to the `PrintCompilation` output. like the following, it would immensely helpful as it would avoid the need to dig up the code to understand what these numbers stand for.
t=elapsed time since JVM start
W=time spent in waiting to be put on compilation queue
Q=time spent in the compilation queue
C=time taken to compile
Id=Compilation Id
Lvl=Compilation level
t W Q C Id Lvl
344 0 1351 3 java.util.Arrays::hashCode (15 bytes) started
345 0 1350 3 java.util.Objects::hash (5 bytes) started
345 0 1352 3 jdk.internal.util.ArraysSupport::hashCode (42 bytes) started
345 0 37 79 1349 3 java.lang.Byte::<init> (10 bytes)
345 0 1353 3 java.lang.Byte::hashCode (8 bytes) started
345 0 77 92 1351 3 java.util.Arrays::hashCode (15 bytes)
345 0 1354 3 java.lang.Byte::hashCode (2 bytes) started
345 0 212 66 1353 3 java.lang.Byte::hashCode (8 bytes)
345 0 276 38 1354 3 java.lang.Byte::hashCode (2 bytes)
345 0 139 167 1352 3 jdk.internal.util.ArraysSupport::hashCode (42 bytes)
345 0 79 354 1348 3 java.lang.invoke.MemberName::hashCode (43 bytes)
345 0 123 107 1350 3 java.util.Objects::hash (5 bytes)
-------------
PR Comment: https://git.openjdk.org/jdk/pull/24984#issuecomment-2847631825
More information about the hotspot-dev
mailing list