JDK-8333262 : Regression 3-4% in SpringBoot startup bmk
  • Type: Bug
  • Component: tools
  • Sub-Component: jshell
  • Affected Version: 23
  • Priority: P4
  • Status: Resolved
  • Resolution: Other
  • Submitted: 2024-05-30
  • Updated: 2025-04-07
  • Resolved: 2025-04-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25
25Resolved
Related Reports
Relates :  
JDK-8327476 - Upgrade JLine to 3.26.1
Description
Seen in the retriage for 23-b23.

Seems to be related to the introduction of JDK-8327476, which might be necessary. Seen on x64 and ARM64.
Comments
Presumably resolved by JDK-8351435.
07-04-2025
After JDK-8351435, the default provider is once again the `java.base` provider. Hence, JLine should no longer be a factor in the test.
07-04-2025
Is there a way for me to run the test? Offhand, if the test initializes (the bundled) JLine (via JShell or System.console()), then it may be slower as that initialization got slower, as we started to using FFM instead of JNI, and the bootstrap of FFM is slower. So far, it seemed like an acceptable compromise between maintenance and usability - this is unlikely to affect JShell too much, and there's a speed up trick for some methods in System.console(). But if the start of JLine would turn out to be more important, we may need to revert to the platform-specific JNI.
08-08-2024
[~jlahoda] Did you have a chance to look at this issue?
23-07-2024