You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/03/08 15:52:00 UTC

[jira] [Comment Edited] (CAMEL-16279) camel-core - Optimize routing engine to reuse internal state objects for GC reduction

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

Claus Ibsen edited comment on CAMEL-16279 at 3/8/21, 3:51 PM:
--------------------------------------------------------------

TODO: Add option to panic check create+acquire vs release when pooled
TODO: optimize internal routing processor (after task)


was (Author: davsclaus):
TODO: Add option to panic check create+acquire vs release when pooled

> 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)