[jira] [Comment Edited] (REEF-788) IMRU Map and Update host tasks take a lot of internal memory

["Dhruv Mahajan (JIRA)" <ji...@apache.org>]

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

Dhruv Mahajan edited comment on REEF-788 at 9/27/15 10:13 PM:
--------------------------------------------------------------

Ohh no no...I am not talking about that data and all. I am talking about something like 

T val 
while(1)
{
val = broadcast.receive();
}

vs.

while(1)
{
T val = broadcast.Receive()
}

Is it clear?


was (Author: dkm2110):
Ohh no no...I am not talking about that data and all. I am talking about something like 

T val 
while(1)
{
val = broadcast.receive();
{

vs.

while(1)
{
T val = broadcast.Receive()
}

Is it clear?

> IMRU Map and Update host tasks take a lot of internal memory
> ------------------------------------------------------------
>
>                 Key: REEF-788
>                 URL: https://issues.apache.org/jira/browse/REEF-788
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF.NET
>    Affects Versions: 0.13
>         Environment: C#
>            Reporter: Dhruv Mahajan
>            Assignee: Dhruv Mahajan
>             Fix For: 0.13
>
>
> Currently in map and update host tasks in IMRU input and output are maintained in memory between the iterations. Also for large sized messages a lot of internal memory is being utilized for pipelining.
> The aim of the jira is to remove the maintenance of input and output between the iterations. Also GC.Collect is used for now to remove memory overheads. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)