-
Bug
-
Resolution: Fixed
-
P3
-
9
It is known from Indify String Concat, Lambdas, and probably Jigsaw that initialization costs for java.lang.invoke infra take a significant time on first access to the infrastructure.
See a simple experiment here:
http://cr.openjdk.java.net/~shade/8086045/indy-startup.txt
The goal for this task is to investigate if we can improve this, or should we conclude the first initialization overheads can be justifiably ignored.
See a simple experiment here:
http://cr.openjdk.java.net/~shade/8086045/indy-startup.txt
The goal for this task is to investigate if we can improve this, or should we conclude the first initialization overheads can be justifiably ignored.
- duplicates
-
JDK-8150717 Bootstrapping invokedynamic call sites can significantly increase time spent in the VM
-
- Closed
-
- is blocked by
-
JDK-8163373 Rewrite GenerateJLIClassesPlugin to avoid reflective calls into java.lang.invoke
-
- Closed
-
- relates to
-
JDK-8251851 InvokerBytecodeGenerator::lookupPregenerated does not support all cases
-
- Open
-
-
JDK-8247536 Support for pre-generated java.lang.invoke classes in CDS static archive
-
- Resolved
-
-
JDK-8152641 Plugin to generate BMH$Species classes ahead-of-time
-
- Resolved
-
-
JDK-8085796 JEP 280: Indify String Concatenation
-
- Closed
-
(1 relates to)