You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2024/07/08 08:08:00 UTC

[jira] [Commented] (CAMEL-20951) Camel 3.22.1 - Observing performance degradation with splitter EIP

    [ https://issues.apache.org/jira/browse/CAMEL-20951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863701#comment-17863701 ] 

Claus Ibsen commented on CAMEL-20951:
-------------------------------------

You need to do your own investigations more, try with 3.21, 3.20, 3.19 and narrow it down, as its a bigger jump between 3.18 and 3.22, and its your app. We dont active support 3.x anymore, all work is focused on 4.x and 3.x is going EOL by end of this year.

> Camel 3.22.1 - Observing performance degradation with splitter EIP
> ------------------------------------------------------------------
>
>                 Key: CAMEL-20951
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20951
>             Project: Camel
>          Issue Type: Task
>    Affects Versions: 3.22.1
>            Reporter: Samhitha
>            Priority: Minor
>
> Observing performance degradation around 20% with Splitter EIP, once we have upgraded from camel 3.18.7 to camel 3.22.1. We are having similar implementation as below, where in data will be split by our logic in "executeSplitter".
>  
> _from("direct:source")_
> _.routeGroup("group")_
> _.routeId("splitterId")_
> _.split()_
> _.method(splitter, "executeSplitter")_
> _.shareUnitOfWork()_
> _.stopOnException()_
> _.toD("direct:destination");_
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)