JDK-8078725 : method adjustments can be done just once for all classes involved into redefinition
- Type: Enhancement
- Component: hotspot
- Sub-Component: jvmti
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-04-28
- Updated: 2024-06-28
- Resolved: 2019-02-22
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 11 | JDK 13 |
|---|---|
| 11.0.25-oracleFixed | 13 b10Fixed  |
Related Reports
|
Blocks :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
The following scalability/performance issues were recently fixed for class redefinition:
https://bugs.openjdk.java.net/browse/JDK-8046246
https://bugs.openjdk.java.net/browse/JDK-8073705
It is going to improve the implementation of the functions:
ConstantPoolCache::adjust_method_entries()
klassVtable::adjust_method_entries()
klassItable::adjust_method_entries()
InstanceKlass::adjust_default_methods()
MemberNameTable::adjust_method_entries()
However, there is more space for improvements:
- The above functions can be run just once for all the redefined classes instead of multiple times after
redefinition of each class in the list (they have no parameters specific for redefined classes anymore)
Comments
|