-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b80
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8136336 | emb-9 | Attila Szegedi | P3 | Resolved | Fixed | team |
JDK-8140967 | 8u91 | Attila Szegedi | P3 | Resolved | Fixed | b01 |
JDK-8134564 | 8u72 | Attila Szegedi | P3 | Resolved | Fixed | b01 |
JDK-8136965 | 8u71 | Attila Szegedi | P3 | Resolved | Fixed | b01 |
JDK-8135186 | 8u66 | Attila Szegedi | P3 | Closed | Fixed | b13 |
JDK-8147336 | emb-8u91 | Attila Szegedi | P3 | Resolved | Fixed | b01 |
JDK-8143811 | emb-8u71 | Unassigned | P3 | Resolved | Fixed | b01 |
This benchmark is reported to exhibit a significant performance regression that was introduced between 8u31 and 8u40.
Running the benchmark with -Xprof indicates a ca. 88 % profile for java.lang.invoke.MethodHandleNatives.setCallSiteTargetNormal; a JFR run (-XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:FlightRecorderOptions=defaultrecording=true,disk=true,dumponexit=true,dumponexitpath=react.jfr,stackdepth=1024) indicates megamorphism around calls to "construct" functions from "instantiateReactComponent" functions.
In principle, this can be due to either Nashorn or java.lang.invoke changes in between 8u31 and 8u40.
JFR log is attached.
- backported by
-
JDK-8134564 Nashorn react.js benchmark performance regression
- Resolved
-
JDK-8136336 Nashorn react.js benchmark performance regression
- Resolved
-
JDK-8136965 Nashorn react.js benchmark performance regression
- Resolved
-
JDK-8140967 Nashorn react.js benchmark performance regression
- Resolved
-
JDK-8143811 Nashorn react.js benchmark performance regression
- Resolved
-
JDK-8147336 Nashorn react.js benchmark performance regression
- Resolved
-
JDK-8135186 Nashorn react.js benchmark performance regression
- Closed
- relates to
-
JDK-8062401 User accessors require boxing and do not support optimistic types
- Resolved