JDK-8043003 : Use strongly referenced generic invokers
- Type: Enhancement
- Component: core-libs
- Sub-Component: jdk.nashorn
- Affected Version: 9
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2014-05-13
- Updated: 2015-01-21
- Resolved: 2014-05-14
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.
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 8 | JDK 9 |
|---|---|
8u40Fixed  |
9 b17Fixed |
Description
We used to store "generic" (all-Object) versions of invokers and constructors in a weak hash map (reasoning was that they're rare, so we shouldn't pay the price of a field in RecompilableScriptFunctionData). Well, turns out we have to, otherwise we get a significant performance hit. I reduced the storage hit by introducing a holder class (GenericInvokers) for the two fields, and only have RecompilableScriptFunctionData reference the holder object. The heuristics here is again that in most cases, functions will not be using the generic invokers.