[jira] [Comment Edited] (HAMA-919) Manage messages per Vertex

["Edward J. Yoon (JIRA)" <ji...@apache.org>]

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

Edward J. Yoon edited comment on HAMA-919 at 2/2/15 11:00 AM:
--------------------------------------------------------------

I'm testing. Actually, retreive() method of direct memory sometimes returns NULL, so I feel it's somewhat unstable.

{quote}
Maybe we should use an other more active one?
{quote}

Do you have/know other solutions similar to Apache Direct Memory?


was (Author: udanax):
I'm testing. Actually, retreive() method of direct memory sometimes returns NULL, so I feel it's somewhat unstable.

{quote}
Maybe we should use an other more active one?
{quote}

Do you have know other good solutions?

> 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, HAMA-919_v03.patch, HAMA-919_v04.patch, HAMA-919_v05.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)