incubator-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 Thu, 15 Dec 2011 23:11:30 GMT


Claudio Martella commented on GIRAPH-45:

Great, we're converge. The BTree is for indexing destination vertices. you want to have all
the messages sent to the same vertex stored all together. It's just a TreeMap with a sample
of the keyset in the flushed file, something similar to the HBase index. The code is complete,
I'm running after a nasty bug and I'll work on integration then.

The question is: do you know a good way to detect memory pressure? I've tried with Runtime.freeMemory()
but it won't work. I was considering using a monitor softreference. any suggestion?
> 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