Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <16873380.214871294418746643.JavaMail.jira@thor>
Date: Fri, 7 Jan 2011 11:45:46 -0500 (EST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-3497) Splitter Component: Setting
 'streaming="true" parallelProcessing="true"' consumes large amounts > of
 heap space for big original messages
In-Reply-To: <4426538.156431294219306379.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen commented on CAMEL-3497:
------------------------------------

trunk on Camel 2.6 in rev 1056380:

I have reduced memory consumption used, which should allow it to be a bit better. But the splitter still uses a bit additional memory due the splitting is based on a copy of the input message for each splitted message.

Ralf you are welcome to test again and see if you can process a bit more than previously.

> Splitter Component: Setting 'streaming="true" parallelProcessing="true"' consumes large amounts > of heap space for big original messages
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3497
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3497
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.5.0
>            Reporter: Ralf Steppacher
>            Assignee: Claus Ibsen
>             Fix For: 3.0.0
>
>
> Setting 'streaming="true" parallelProcessing="true"' consumes large amounts of heap space for big original messages. E.g. 1024m of heap is not enough to process an 80Mb with 500'000 lines, splitting it line by line.
> The problem seems to be the ArrayList in MulticastProcessor line 224. It contains a Future<Exchange> object for every token delivered by the java.util.Scanner. The list is only cleared (going out of scope) after all Future objects have been completed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.