camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-11358) Optimise - Event listener to avoid copy on write array list
Date Mon, 29 May 2017 13:04:04 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-11358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-11358.
---------------------------------
    Resolution: Won't Fix

Ah the memory size between the regular array list and the copy are neglible. I wonder if the
JVM could not optimize this the for looping to not be iterator based but just index based
which wont require object allocations of the iterator.

> Optimise - Event listener to avoid copy on write array list
> -----------------------------------------------------------
>
>                 Key: CAMEL-11358
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11358
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.20.0
>
>
> See CAMEL-5531
> After camel is started we should switch to another implementation of the event listern
list, as when you iterate it then the copy on write will create a new iterator. And we iterate
a lot during routing when Camel emits events for each step a message takes in the route graph



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message