You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@reef.apache.org by "Brian Cho (JIRA)" <ji...@apache.org> on 2015/08/06 11:28:05 UTC

[jira] [Resolved] (REEF-179) Solve the large memory footprint problem due to multiple serializations during call to an operator

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

Brian Cho resolved REEF-179.
----------------------------
    Resolution: Fixed

> Solve the large memory footprint problem due to multiple serializations during call to an operator
> --------------------------------------------------------------------------------------------------
>
>                 Key: REEF-179
>                 URL: https://issues.apache.org/jira/browse/REEF-179
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF-IO, REEF.NET, Wake
>            Reporter: Dhruv Mahajan
>            Assignee: Dhruv Mahajan
>              Labels: IWritableGroupComm
>             Fix For: 0.12
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Right now  during each communication call, there are three serialization steps happening where actual data/message to pass is encoded again and again leading to larger memory footprints. We would like to optimize it.



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