[ 
https://issues.apache.org/jira/browse/GIRAPH-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629536#comment-13629536
 ] 

Hudson commented on GIRAPH-616:
-------------------------------

Integrated in Giraph-trunk-Commit #911 (See 
[https://builds.apache.org/job/Giraph-trunk-Commit/911/])
    GIRAPH-616: Decouple vertices and edges in DiskBackedPartitionStore and 
avoid writing back edges when the algorithm does not change topology. (Revision 
228edbbd798f7718a5a7ccbcfd35c22e812be761)
GIRAPH-616 (Revision 39f3591365cbe15b74c82574787d0592681d8ba5)

     Result = SUCCESS
claudio : 
http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=228edbbd798f7718a5a7ccbcfd35c22e812be761
Files : 
* giraph-core/src/main/java/org/apache/giraph/conf/GiraphConstants.java
* 
giraph-core/src/main/java/org/apache/giraph/partition/DiskBackedPartitionStore.java
* giraph-core/src/main/java/org/apache/giraph/conf/GiraphConfiguration.java

claudio : 
http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=39f3591365cbe15b74c82574787d0592681d8ba5
Files : 
* CHANGELOG

                
> Decouple vertices and edges in DiskBackedPartitionStore and avoid writing 
> back edges when the algorithm does not change topology.
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GIRAPH-616
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-616
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Claudio Martella
>            Assignee: Claudio Martella
>         Attachments: GIRAPH-616.diff, GIRAPH-616.diff
>
>
> Many algorithms work on a static graph. In these cases, when running 
> out-of-core graph we end up writing back the edges that have not changed 
> since we read them. By decoupling vertices and edges, we can write back only 
> the freshly computed vertex values.

--
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

Reply via email to