Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 12
Affects Version/s: None
Component/s: hotspot
Labels:

Subcomponent:
runtime
Resolved In Build:
b07

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8230512	11.0.6	Claes Redestad	P4	Resolved	Fixed	b01

Archiving the IntegerCache into the CDS archive turns out to be profitable.

Experiments shows ~1M fewer instructions in the default case (<0.5ms), with an implementation that deals gracefully with cases where a larger or smaller cache than archived has been requested.

In case a larger cache is archived and then requested, the gain is greater since the loading/mapping of the cache happens in constant rather than linear time, observing a ~150ms speedup on something like this:

java -Xshare:dump -Djava.lang.Integer.IntegerCache.high=65535
java -Xshare:on -Djava.lang.Integer.IntegerCache.high=65535 HelloWorld

backported by

JDK-8230512 Archive the Integer.IntegerCache

Resolved

is blocked by

JDK-8207263 Store the Configuration for system modules into CDS archive

Resolved

relates to

JDK-8213033 Archive remaining primitive box caches

Resolved

JDK-8343019 Primitive caches must use boxed instances from the archive

Closed

JDK-8202035 Archive the set of ModuleDescriptor and ModuleReference objects for observable system modules with unnamed initial module

Resolved

JDK-8206115 Use shared macros for JavaClasses::compute_offsets and MetaspaceShared::serialize_well_known_classes

Resolved

JDK-8212995 Place the Integer.IntegerCache and cached Integer objects in the closed archive heap region

Resolved

(2 relates to)

Assignee:: Claes Redestad

Reporter:: Claes Redestad

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2018-08-08 02:50

Updated:: 2024-10-28 03:04

Resolved:: 2018-08-13 10:28

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates