[
https://issues.apache.org/jira/browse/CAMEL-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255169#comment-14255169
]
Claus Ibsen commented on CAMEL-8113:
------------------------------------
I wonder if we can make a way to detect if we have a type converter or not for
the from -> to class type combo, without having to create a new object. eg as
we do today to crate a new TypeMapping instance.
Not sure if a Class[2] type is faster, or slower. As we would need to create a
Class[] array instance using new anyway.
> Look into optimize Camels type converter registry lookup
> --------------------------------------------------------
>
> Key: CAMEL-8113
> URL: https://issues.apache.org/jira/browse/CAMEL-8113
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.15.0, Future
>
>
> See this blog
> http://tech.ticketmaster.com/2014/12/01/getting-over-the-performance-hump-with-apache-camel/
> There is some findings about how Camel's TC may produce GC overhead, and also
> the CXF MessageContextList.
> Yeah unfortuntalte camel-cxf had that MessageContextList from the beginning
> which has been a cause of pain ever since.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
