You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Avery Ching (JIRA)" <ji...@apache.org> on 2015/07/06 19:35:05 UTC
[jira] [Commented] (GIRAPH-1019) Optimizing and debugging vertex
mutation
[ https://issues.apache.org/jira/browse/GIRAPH-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615355#comment-14615355 ]
Avery Ching commented on GIRAPH-1019:
-------------------------------------
https://reviews.facebook.net/D39783
> Optimizing and debugging vertex mutation
> ----------------------------------------
>
> Key: GIRAPH-1019
> URL: https://issues.apache.org/jira/browse/GIRAPH-1019
> Project: Giraph
> Issue Type: Improvement
> Components: graph
> Reporter: Hassan Eslami
> Labels: core, migration, multi-threading
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Currently vertex mutations happen while preparing a superstep execution in a single-threaded manner. This is extremely inefficient specially for the case of out-of-core as we have to go over all the partitions, load them, and test if they have any applicable mutation. Also, there is an unexpected behavior in cases where a mutation happen to a vertex and some messages being delivered to that vertex at the same time (current implementation fails the job in that case).
> In order to fix/optimize this, mutations should happen in a multi-threaded fashion right before start of processing of a partition. Also, while partition migration happens, mutation requests should migrate along with the partition and its messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)