-
Enhancement
-
Resolution: Fixed
-
P4
-
9
-
None
-
b92
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8143539 | emb-9 | Attila Szegedi | P4 | Resolved | Fixed | team |
I profiled loading of test/script/basic/compile-octane.js; it's one of the longest-taking scripts in our tests. Surprisingly, two large hot spots presented themselves, both calling Class.forName: one in Context.forStructureClass another for Type.typeFor. Since both methods will load classes that will be retained in memory, adding a cache in front of them is a no-brainer. Doing so caused the first-time execution (significant in our tests) to drop from 34s to 28s. Warmed up time from repeating the loading in an infinite loop (not too significant in our case) dropped from 18s to 13s.
Whole test suite execution also benefits; on my machine it went down from 12m30s to 10m30s.
Whole test suite execution also benefits; on my machine it went down from 12m30s to 10m30s.
- backported by
-
JDK-8143539 Cache Class.forName for permanently loaded classes
-
- Resolved
-