giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-41) Change graph mutation RPC API to a kind of message
Date Sat, 30 Jun 2012 14:21:44 GMT


Hyunsik Choi commented on GIRAPH-41:

In BasicRPCCommunication, this issue is relevant. However, NettyWorkerClient already deals
with the graph mutation requests as a kind of message via sendMutationCache. Later, if we
remove Hadoop RPC (GIRAPH-200), this issue will not relevant. After GIRAPH-200 is resolved,
I'll close this issue as 'Won't fix'.
> Change graph mutation RPC API to a kind of message
> --------------------------------------------------
>                 Key: GIRAPH-41
>                 URL:
>             Project: Giraph
>          Issue Type: Improvement
>          Components: bsp
>            Reporter: Hyunsik Choi
> Graph mutation functions (e.g., addVertexRequest, addEdgeRequest..) directly invoke RPC
> In processing, these RPC calls may incur delays caused by TCP round-trip time and communication
overheads caused by frequent RPC call. Especially, when many workers try to mutate vertices
and edges simultaneously, the synchronization overheads may also occur in receiving sides.
It may become intensive as the size of cluster increases.
> If we change graph mutation API to a kind of messages, it would be more efficient. If
possible, graph mutation message API and data messages API (i.e., sendMsg)can be integrated
into one message passing API.
> What do you think about that?

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