[
https://issues.apache.org/jira/browse/CAMEL-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669115#comment-13669115
]
Claus Ibsen edited comment on CAMEL-6377 at 7/28/13 1:12 PM:
-------------------------------------------------------------
We can/shoulder optimize SendProcessor (eg the to in routes) which is used a
lot. It uses a producer cache under the hood for sending. Though this logic is
most really needed for producer that needs to be pooled etc. We can optimize
the logic and have a faster executing for non pooled producers.
This can reduce 4 stackframes to 1 instead. *done*
was (Author: davsclaus):
We can/shoulder optimize SendProcessor (eg the to in routes) which is used
a lot. It uses a producer cache under the hood for sending. Though this logic
is most really needed for producer that needs to be pooled etc. We can optimize
the logic and have a faster executing for non pooled producers.
This can reduce 4 stackframes to 1 instead.
> Optimize routing engine to reduce stack frames in use during routing and
> reduce callbacks
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-6377
> URL: https://issues.apache.org/jira/browse/CAMEL-6377
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.12.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.12.0
>
>
> We can optimize the Camel routing engine internally, and redue the need for
> wrapping processors (those internally used for cross cutting functionality)
> where they would wrap each other one by one; which then results in larger
> call stacks during routing.
> This also shows to end users when stacktraces is being logged etc, as they
> tend to be a bit longer with many internal calls.
> Though the JVM optimizes this at runtime as it can inline the calls and
> whatnot. But the stacktraces is still shown expanded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
