JDK-8174749 : Use hash table/oops for MemberName table
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 8u121,9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2017-02-10
  • Updated: 2021-04-26
  • Resolved: 2017-05-27
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 10
10 b21Fixed
Related Reports
Relates :  
JDK-8221437 - assert(java_lang_invoke_ResolvedMethodName::vmtarget(resolved_method()) == m()) failed: Should not change after link resolution
Relates :  
JDK-8249719 - MethodHandle performance suffers from bad ResolvedMethodTable hash function
Relates :  
JDK-8264816 - Weak handles leak causes GC to take longer
Relates :  
JDK-8012162 - JSR-292: reference to MNT in InstanceKlass impacts a footprint
Relates :  
JDK-8184672 - [ppc64] The fix for '8174749: Use hash table/oops for MemberName table' is broken on ppc64
Relates :  
JDK-8166852 - JavaScript engine eval() method causes JVM Young GC to pauses seconds
Relates :  
JDK-8152271 - MemberNameTable doesn't purge stale entries
Relates :  
JDK-8013267 - move MemberNameTable from native code to Java heap, use to intern MemberNames
Relates :  
JDK-8181172 - Use ResolvedMethodName directly instead of MemberName
Relates :  
JDK-8181173 - Create ResolvedMethodName table with Klass* as key
Relates :  
JDK-8162795 - [REDO] MemberNameTable doesn't purge stale entries
Description
Use hash table/oops for MemberName table

The current implementation based on growable array and jweaks, suffers from performance issues that were subjects to several efforts covered by the related issues.

Re-implementing the MemberName table using hash tables/oops, just like StringTable, should solve the issues.