giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (Commented) (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-45) Improve the way to keep outgoing messages
Date Mon, 28 Nov 2011 06:52:40 GMT


Arun Suresh commented on GIRAPH-45:

+1 for using an external datastore

I was faced with a similar issue when I was implementing pregel in Erlang. Since the base
Erlang distribution came with is own in process db, it wasnt much of a problem. Although I
did take a look at [Tokyo Cabinet|]. Its blazingly fast.

Why dont we take a look a [Apache Derby|] or [HSQLDB|]
before we try leveldb. They are both pure Java implementations and they have decent performance
and they've around much longer. 
> Improve the way to keep outgoing messages
> -----------------------------------------
>                 Key: GIRAPH-45
>                 URL:
>             Project: Giraph
>          Issue Type: Improvement
>          Components: bsp
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
> As discussed in GIRAPH-12(, I think that there is a potential problem
to cause out of memory when the rate of message generation is higher than the rate of message
flush (or network bandwidth).
> To overcome this problem, we need more eager strategy for message flushing or some approach
to spill messages into disk.
> The below link is Dmitriy's suggestion.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message