-
Type:
Bug
-
Status: Resolved
-
Priority:
P4
-
Resolution: Fixed
-
Affects Version/s: 11, 13, 15
-
Fix Version/s: 15
-
Component/s: infrastructure
-
Subcomponent:
-
Resolved In Build:b24
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8256398 | 11.0.10 | Magnus Ihse Bursie | P4 | Resolved | Fixed | b03 |
The linking of the JDK image using the jlink tool takes a considerable amount of time. However, the jlink tool is classified as a "small java" tool in the build script. This should only be used on quick small tools where a long startup time has a measurable performance impact. Clearly this does not apply to jlink.
The effect of removing the small tool flags are most pronounced when running a slowdebug build. Robbin Ehn, which made me aware of this, reduced the running time of jlink from 36 to 21 seconds on his machine by removing the "small" flags. On a release build, the effect is much less noticeable, but it's still worth fixing.
The effect of removing the small tool flags are most pronounced when running a slowdebug build. Robbin Ehn, which made me aware of this, reduced the running time of jlink from 36 to 21 seconds on his machine by removing the "small" flags. On a release build, the effect is much less noticeable, but it's still worth fixing.
- backported by
-
JDK-8256398 jlink should not be treated as a "small" tool
-
- Resolved
-