JDK-8059879 : Type profile pollution due to LF sharing causes peak performance regressions
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.
Type profile pollution due to LambdaForm sharing causes significant performance regressions on Octane/Nashorn.
GWT branch frequencies pollution is tracked by JDK-8059877.
Additional performance analysis didn't reveal any performance issues caused by type profile pollution with LF sharing.
Further inverstigations showed that type profile pollution doesn't affect performance in a significant way.
Lower the priority: P2 (HLH) => P4 (MLH).
Will close if no regressions are caused by that. It's possible after all regressions caused by branch frequencies pollution are fixed.
One way to solve the problem is to prepare customized bytecodes for indy call sites.