[
https://issues.apache.org/jira/browse/CAMEL-16452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-16452.
---------------------------------
Resolution: Won't Do
> camel-core - Optimized ThreadPool with reusable tasks
> -----------------------------------------------------
>
> Key: CAMEL-16452
> URL: https://issues.apache.org/jira/browse/CAMEL-16452
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Minor
>
> Camel has been optimized so much that profiling now reveals that when using
> JDKs thread pool then every time a a task is submitted then a FutureTask is
> created which then costs object allocations.
> We can look at having a PooledFutureTask where you can execute runAndReset
> instead. However this prevents using future get to get a result. But in some
> use-cases we do not use this, such as WireTap EIP and (and maybe some other
> EIPs)
> java.util.concurrent.FutureTask#runAndReset
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
