You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Otavio Rodolfo Piske (Jira)" <ji...@apache.org> on 2023/05/25 11:20:00 UTC
[jira] [Resolved] (CAMEL-19319) Type check misses
[ https://issues.apache.org/jira/browse/CAMEL-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Otavio Rodolfo Piske resolved CAMEL-19319.
------------------------------------------
Resolution: Fixed
Incidences of type check misses still exist, but they have been significantly reduced in the current code. Therefore, closing.
> Type check misses
> -----------------
>
> Key: CAMEL-19319
> URL: https://issues.apache.org/jira/browse/CAMEL-19319
> Project: Camel
> Issue Type: Task
> Components: came-core
> Affects Versions: 4.0-M2
> Reporter: Otavio Rodolfo Piske
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Fix For: 4.0-RC1
>
> Attachments: type-check-report.txt
>
>
> 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|https://github.com/RedHatPerf/type-pollution-agent] can be used to identify where this happen. A report is attached to this ticket.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)