Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P3
Fix Version/s: 10
Affects Version/s: 8u121, 9
Component/s: hotspot
Labels:
- metadata

Subcomponent:
runtime
Resolved In Build:
b21
CPU:

generic
OS:

generic

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.

relates to

JDK-8184672 [ppc64] The fix for '8174749: Use hash table/oops for MemberName table' is broken on ppc64

Resolved

JDK-8162795 [REDO] MemberNameTable doesn't purge stale entries

Resolved

JDK-8152271 MemberNameTable doesn't purge stale entries

Closed

JDK-8013267 move MemberNameTable from native code to Java heap, use to intern MemberNames

Open

JDK-8181172 Use ResolvedMethodName directly instead of MemberName

Open

JDK-8181173 Create ResolvedMethodName table with Klass* as key

Closed

JDK-8221437 assert(java_lang_invoke_ResolvedMethodName::vmtarget(resolved_method()) == m()) failed: Should not change after link resolution

Resolved

JDK-8249719 MethodHandle performance suffers from bad ResolvedMethodTable hash function

Resolved

JDK-8264816 Weak handles leak causes GC to take longer

Resolved

JDK-8166852 JavaScript engine eval() method causes JVM Young GC to pauses seconds

Closed

JDK-8012162 JSR-292: reference to MNT in InstanceKlass impacts a footprint

Closed

(6 relates to)

Assignee:: Coleen Phillimore

Reporter:: Gerard Ziemski

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2017-02-10 09:31

Updated:: 2021-04-26 05:10

Resolved:: 2017-05-27 07:22

Details

Description

Attachments

Issue Links

Activity

People

Dates