[
https://issues.apache.org/jira/browse/CAMEL-19398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727922#comment-17727922
]
Claus Ibsen commented on CAMEL-19398:
-------------------------------------
Otavio can you point to some of the tests that you use that causes these
exceptions ?
The YourKit profiler (works in IDEA too) has a great capture where it can
capture all thrown exceptions so you can trace back where they happen. I used
this in the past to find some exceptions on startup we could do in a nicer way
without throwing and catching.
> camel-core: type converter performs slowly due to exception-based flow control
> ------------------------------------------------------------------------------
>
> Key: CAMEL-19398
> URL: https://issues.apache.org/jira/browse/CAMEL-19398
> Project: Camel
> Issue Type: Task
> Components: camel-core
> Reporter: Otavio Rodolfo Piske
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Attachments:
> profile-cbr-text-2023-05-29-4.0.0-SNAPSHOT-2023-05-29-070154.html
>
>
> It looks like, when consuming data of different types, our type converters
> perform extremely slowly. For instance, in a test sending data of different
> types (Strings, Integers, Beans, etc) in a machine that easily routes 800k
> exchanges per sec, with a CBR, it decreases to as much as 49k exchanges/sec.
> Analyzing the frame graphs for this (attached) we can see that there is a
> significant amount of time spent dealing with handling exceptions.
> Camel's ability to use the processing power available in the machine seems to
> be severely affected by this:
> {noformat}
> 39132464047 instructions # 0.80 insn per cycle
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
