Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hama-dev@incubator.apache.org
Date: Sat, 28 Apr 2012 07:15:45 +0000 (UTC)
From: "Edward J. Yoon (JIRA)" <jira@apache.org>
To: hama-dev@incubator.apache.org
Message-ID: 
 <1443548407.5993.1335597345360.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <752321656.14192.1330724757503.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HAMA-521) Improve message buffering to save
 memory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Edward J. Yoon updated HAMA-521:
--------------------------------

    Status: Open  (was: Patch Available)

I can't build with this patch.
                
> Improve message buffering to save memory
> ----------------------------------------
>
>                 Key: HAMA-521
>                 URL: https://issues.apache.org/jira/browse/HAMA-521
>             Project: Hama
>          Issue Type: Sub-task
>    Affects Versions: 0.5.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>             Fix For: 0.6.0
>
>         Attachments: HAMA-521.patch, HAMA-521_1.patch, HAMA-521_2.patch, HAMA-521_3.patch, HAMA-521_final.patch, mytest.patch
>
>
> Suraj and I had a bit of discussion about incoming and outgoing message buffering and scalability.
> Currently everything lies on the heap, causing huge amounts of GC and waste of memory. We can do better.
> Therefore we need to extract an abstract Messenger class which is directly under the interface but over the compressor class.
> It should abstract the use of the queues in the back (currently lot of duplicated code) and it should be backed by a sequencefile on local disk.
> Once sync() starts it should return a message iterator for combining and then gets put into a message bundle which is send over RPC.
> On the other side we get a bundle and looping over it putting everything into the heap making it much larger than it needs to be. Here we can also flush on disk because we are just using a queue-like method to the user-side.
> Plus points:
> In case we have enough heap (see our new metric system), we can also implement a buffering technology that is not flushing everything to disk.
> Open questions:
> I don't know how much slower the whole system gets, but it would save alot of memory. Maybe we should first evaluate if it is really needed.
> In any case, the refactoring of the duplicate code in the messengers is needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira