Class redefinition walks the code cache for every class redefined (twice). It could simply do one walk at the end of the entire redefinition.
The performance cost of walking code caches have been seen in using redefinition.
- relates to
-
JDK-8078725 method adjustments can be done just once for all classes involved into redefinition
-
- Resolved
-
-
JDK-8218601 [AOT] Crash in AOTCodeHeap::mark_evol_dependent_methods
-
- Closed
-
-
-
- Closed
-