camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-6377) Optimize routing engine to reduce stack frames in use during routing and reduce callbacks
Date Thu, 23 May 2013 18:29:20 GMT

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

Guillaume Nodet edited comment on CAMEL-6377 at 5/23/13 6:28 PM:
-----------------------------------------------------------------

Two other things that I have started doing locally:
  * for direct derived classes of AsyncDelegateProcessor, replace super.process(exchange,
callback) with processor.process(exchange, callback) as it avoids a useless method call
  * fix the remaining processors not implementing AsyncProcessor to avoid wrapping (SetBody,
Transform, Aggregate, Marshall ...)

I can work on that if nobody has any objection or wants to do it.

                
      was (Author: gnt):
    Two other things that I have started doing locally:
  * for direct derived classes of AsyncDelegateProcessor, replace super.process(exchange,
callback) with processor.process(exchange, callback) as it avoids a useless call
  * fix the remaining processors not implementing AsyncProcessor to avoid wrapping
I can work on that if nobody has any objection or wants to do it.

                  
> 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