Major Description
Within the core code there are many circumstances where the type checks performed by our code, causes the JVM to miss a cache hit and enter a slower code path.
This can be caused when type check (such as an instanceof check) fails for a class instance which implements multiple types (incurring in both a cache a traversal of the secondary supers ArrayList).
The type-pollution-agent can be used to identify where this happen. A report is attached to this ticket.
Attachments
Attachments
Issue Links
- links to