incubator-giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (Commented) (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-45) Improve the way to keep outgoing messages
Date Tue, 15 Nov 2011 20:16:53 GMT


Jakob Homan commented on GIRAPH-45:

Another consideration is, in situations where a combiner has been defined and has a significant
effect, that the destination worker is likely to have more messages than any other node, so
by shipping them to it early, we'll save more space by running the combiner against all those
messages.  ie, if four workers each have 10 messages and combine each of those sets to 1 message,
we still have four messages.  If we then immediately ship them to the destination worker and
combine, we would end up with 1 final message to be stored for the next superstep.
> 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