[
https://issues.apache.org/jira/browse/CAMEL-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293002#comment-17293002
]
Claus Ibsen commented on CAMEL-16279:
-------------------------------------
Do you want to trade a little bit cpu overhead with a pool for take/release and
keep memory more constant, vs use less cpu but allocate more memory that needs
GC
I think about storing X objects on the PooledExchange with some indexing that
the internal routing engine can use to access by index its "own instance" so
they are threadsafe and we dont need the object allocations but that model
works best for a more "static" route path
but would be kinda cool so you can warmup the route paths, and know how many
you need and then be "ready" for incoming traffic
> camel-core - Optimize routing engine to reuse internal state objects for GC
> reduction
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-16279
> URL: https://issues.apache.org/jira/browse/CAMEL-16279
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.9.0
>
> Attachments: Screenshot 2021-03-01 at 17.24.47.png
>
>
> If we use pooled exchanges, then we can try to experiment with storing the
> nessasary internal objects used during routing on the exchange (in some new
> place) so the routing engine can reuse these objects without cause object
> allocations.
> This makes memory usage more stable and reduces the GC.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
