giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitay Joffe (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GIRAPH-41) Change graph mutation RPC API to a kind of message
Date Wed, 07 Nov 2012 16:49:12 GMT

     [ https://issues.apache.org/jira/browse/GIRAPH-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nitay Joffe resolved GIRAPH-41.
-------------------------------

    Resolution: Won't Fix
    
> Change graph mutation RPC API to a kind of message
> --------------------------------------------------
>
>                 Key: GIRAPH-41
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-41
>             Project: Giraph
>          Issue Type: Improvement
>          Components: bsp
>            Reporter: Hyunsik Choi
>
> Graph mutation functions (e.g., addVertexRequest, addEdgeRequest..) directly invoke RPC
functions. 
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message