[
https://issues.apache.org/jira/browse/CAMEL-11351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11351:
--------------------------------
Description:
When using producer template / producer cache and have a result processor to
convert the result to X then it wraps using a set of internal processors / uow
etc which creates a new objects which we can avoid.
This was introduced by CAMEL-10308
We can further optimise this to avoid creating a new instance of internal
processor but use a shared instance. This is a hot spot as ProducerCache is
used by producer template, and EIPs that sends to endpoints such as to and toD
etc.
was:
When using producer template / producer cache and have a result processor to
convert the result to X then it wraps using a set of internal processors / uow
etc which creates a new objects which we can avoid.
This was introduced by CAMEL-10308
> Optimize - ProducerCache - Avoid creating new processor for each send if
> result processor
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-11351
> URL: https://issues.apache.org/jira/browse/CAMEL-11351
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.20.0
>
> Attachments: after.png, Screen Shot 2017-05-28 at 09.51.48.png
>
>
> When using producer template / producer cache and have a result processor to
> convert the result to X then it wraps using a set of internal processors /
> uow etc which creates a new objects which we can avoid.
> This was introduced by CAMEL-10308
> We can further optimise this to avoid creating a new instance of internal
> processor but use a shared instance. This is a hot spot as ProducerCache is
> used by producer template, and EIPs that sends to endpoints such as to and
> toD etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
