-
Bug
-
Resolution: Fixed
-
P3
-
25, 26
-
b06
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8362051 | 25.0.1 | Erik Gahlin | P3 | Resolved | Fixed | b02 |
JDK-8361601 | 25 | Erik Gahlin | P3 | Resolved | Fixed | b31 |
JEP 520: JFR Method Timing & Tracing added capabilities to time individual methods, but the view representation and the data can be confusing:
- The event description should state that the measured values are approximations and that not just CPU time is measured.
The measured time may become 0 due to a low-resolution clock. It's better not to include those values when determining the minimum value.
- Ensure that the minimum and maximum values are reasonable when compared to the average.
- Use "Minimum" and "Maximum" instead of "Min." and "Max." in the method-timing view to create some space between columns.
- The event description should state that the measured values are approximations and that not just CPU time is measured.
The measured time may become 0 due to a low-resolution clock. It's better not to include those values when determining the minimum value.
- Ensure that the minimum and maximum values are reasonable when compared to the average.
- Use "Minimum" and "Maximum" instead of "Min." and "Max." in the method-timing view to create some space between columns.
- backported by
-
JDK-8361601 JFR: Min and max time in MethodTime event is confusing
-
- Resolved
-
-
JDK-8362051 JFR: Min and max time in MethodTime event is confusing
-
- Resolved
-
- duplicates
-
JDK-8361969 JFR: Missing documentation for MethodTiming and MethodTrace events
-
- Closed
-
- links to
-
Commit(jdk25) openjdk/jdk/b3b55953
-
Commit(master) openjdk/jdk/f3e0588d
-
Review(jdk25) openjdk/jdk/26145
-
Review(master) openjdk/jdk/26112
(2 links to)