giraph-dev mailing list archives

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


Claudio Martella commented on GIRAPH-45:

Yes, exactly. Given that you'd have to hit the network anyway (so let's ignore that cost),
the problem is whether the other end would store them on disk or not. If so, it can make sense
for the sender to hit the disk and then send them to the other end at the beginning of next
superstep, and that node would have to process them as they come. This would mean the disk
is hit once on the node generating the messages, but then the other end would have to implement
a pull-model. The other option, the push-model, would still require the second end-point to
disk the disk twice.
> 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