camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-6377) Optimize routing engine to reduce stack frames in use during routing and reduce callbacks
Date Fri, 24 May 2013 07:52:22 GMT

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

Claus Ibsen commented on CAMEL-6377:
------------------------------------

And if we really wanna dig deep, then we can look at where we use code like this:
{code}
            AsyncProcessor async = AsyncProcessorConverterHelper.convert(processor);
{code}

The problem is that then we would need to deal with both plain Processor and AsyncProcessor
in the EIPs and call them accordingly, either plain or async. And that complicates the EIP
code a bit more. Where as the code above makes it easy for the EIPs.
                
> 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

Mime
View raw message