Mailing-List: contact dev-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hama.apache.org
Date: Tue, 27 Jan 2015 06:18:35 +0000 (UTC)
From: "Edward J. Yoon (JIRA)" <jira@apache.org>
To: dev@hama.apache.org
Message-ID: <JIRA.12741788.1410875393000.181398.1422339515154@Atlassian.JIRA>
In-Reply-To: <JIRA.12741788.1410875393000@Atlassian.JIRA>
References: <JIRA.12741788.1410875393000@Atlassian.JIRA>
 <JIRA.12741788.1410875393541@arcas>
Subject: [jira] [Commented] (HAMA-919) Manage messages per Vertex
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Edward J. Yoon commented on HAMA-919:
-------------------------------------

note: Bugs were in my patch.

> Manage messages per Vertex
> --------------------------
>
>                 Key: HAMA-919
>                 URL: https://issues.apache.org/jira/browse/HAMA-919
>             Project: Hama
>          Issue Type: Improvement
>          Components: graph
>    Affects Versions: 0.6.4
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>            Priority: Blocker
>             Fix For: 0.7.0
>
>         Attachments: HAMA-919_v01.patch, HAMA-919_v02.patch, test.patch
>
>
> As I described in mailing list, we need to manage the messages per Vertex. 
> Currently, sender-side creates and sends the GraphJobMessage object per each message, receiver-side groups messages by Vertex. To simplify grouping process, we used sorting and sequential processing.
> If we manage the outgoing messages per Vertex, we don't need to use the sorted message queue. So we can improve the memory efficiency and the performance by multi-threading.


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