-
Enhancement
-
Resolution: Incomplete
-
P4
-
9
When JVMD starts it retransforms loaded classes.
We saw that retransformation takes a long time per class (in certain cases it took about 1 second per class).
The amount of retransformed classes varies according to the environment and to the time JVMD was deployed (if it is deployed right after jvm satrtup less classes will be retransformed then if it is restranformed later).
In the current implementation retransformation is done one class at a time, but the problem occurs also if all the classes are retransformed at the same time.
The retransformed classes do NOT have large amount of attributes or methods
We saw that retransformation takes a long time per class (in certain cases it took about 1 second per class).
The amount of retransformed classes varies according to the environment and to the time JVMD was deployed (if it is deployed right after jvm satrtup less classes will be retransformed then if it is restranformed later).
In the current implementation retransformation is done one class at a time, but the problem occurs also if all the classes are retransformed at the same time.
The retransformed classes do NOT have large amount of attributes or methods
- relates to
-
JDK-8139551 Scalability problem with redefinition - multiple code cache walks
- Resolved
-
JDK-8078725 method adjustments can be done just once for all classes involved into redefinition
- Resolved