Claudio Martella commented on GIRAPH-45:

Sorry, I'll clarify my last sentence. The other option, the push-model, would 
still require the second end-point to hit the disk (as it could not be possible 
to keep them in memory, otherwise we wouldn't be discussing this at all) and 
that would be the second time in total. Maybe a third option would be a 
push-model where the end-point commands the amount of data and the timing of 
the push. (Something like: "hey, I'm ready, give me the first 5 messages" and 
then "hey, i'm ready for the next 5" and so on).
> Improve the way to keep outgoing messages
> -----------------------------------------
>                 Key: GIRAPH-45
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-45
>             Project: Giraph
>          Issue Type: Improvement
>          Components: bsp
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
> As discussed in GIRAPH-12(http://goo.gl/CE32U), 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.
> https://issues.apache.org/jira/browse/GIRAPH-12?focusedCommentId=13116253&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13116253

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to