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

Posted to dev@reef.apache.org by "Dhruv Mahajan (JIRA)" <ji...@apache.org> on 2015/04/16 20:42:00 UTC

[jira] [Updated] (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 ]

Dhruv Mahajan updated REEF-179:
-------------------------------
    Issue Type: Improvement  (was: Sub-task)
        Parent:     (was: REEF-154)

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