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 12:10:00 UTC
[jira] [Updated] (CAMEL-19058) Type check scalability issue
[ https://issues.apache.org/jira/browse/CAMEL-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Otavio Rodolfo Piske updated CAMEL-19058:
-----------------------------------------
Component/s: camel-seda
camel-core
camel-disruptor
> 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)