[
https://issues.apache.org/jira/browse/HAMA-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301156#comment-14301156
]
Anastasis Andronidis commented on HAMA-919:
-------------------------------------------
>From various conversations I heard about projects that work as key-value
>storages:
1) Memcached
2) Ehcache
3) MapDB (has support for both off-heap and hard drive storage, we could
exploit that for scaling large datasets)
I have no experience with any of those projects though.
> 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)
