[
https://issues.apache.org/jira/browse/CAMEL-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743694#comment-17743694
]
Otavio Rodolfo Piske commented on CAMEL-19058:
----------------------------------------------
Oh. I think we can close this for now. There may be other cases of the type
check issue, but I can create separate tickets as needed.
> Type check scalability issue
> ----------------------------
>
> Key: CAMEL-19058
> URL: https://issues.apache.org/jira/browse/CAMEL-19058
> Project: Camel
> Issue Type: Task
> Components: camel-core, camel-disruptor, camel-seda
> Reporter: Otavio Rodolfo Piske
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Attachments: sample-trace-for-m1.txt
>
>
> Camel 3.x as well as 4.0.0-M1 reportedly have multiple cases of the
> type-check scalability described in [this
> post|https://redhatperf.github.io/post/type-check-scalability-issue/].
> This can affect the the scalability of Camel when running with multiple
> threads and incur in extra unnecessary work.
> See the attachment [^sample-trace-for-m1.txt] for a report of the possible
> cases for M1 (triggered by running a simple application using seda).
> The initial set of patches for CAMEL-15105 have helped a great deal to remove
> these, but there's still a few to resolve.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
