[
https://issues.apache.org/jira/browse/GIRAPH-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098551#comment-13098551
]
Hyunsik Choi commented on GIRAPH-12:
------------------------------------
Jake,
Thank you for recommendation :)
Avery,
Thank you for informing me.
I post my progress of this issue.
Recently, I have implemented and tested a lightweight RPC implementation based
on netty and protocol-buffer, which resembles to YarnRPC. Apparently, an
alternative RPC can give a performance gain.
finagle is very mature in compared to my own. It would be better solution. I'll
test my own and finagle together. As soon as completed tests, I'll post the
results.
> Investigate communication improvements
> --------------------------------------
>
> Key: GIRAPH-12
> URL: https://issues.apache.org/jira/browse/GIRAPH-12
> Project: Giraph
> Issue Type: Improvement
> Reporter: Avery Ching
> Assignee: Hyunsik Choi
> Priority: Minor
>
> Currently every worker will start up a thread to communicate with every other
> workers. Hadoop RPC is used for communication. For instance if there are
> 400 workers, each worker will create 400 threads. This ends up using a lot
> of memory, even with the option
> -Dmapred.child.java.opts="-Xss64k".
> It would be good to investigate using frameworks like Netty or custom roll
> our own to improve this situation. By moving away from Hadoop RPC, we would
> also make compatibility of different Hadoop versions easier.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
