Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Fri, 25 Oct 2013 03:51:30 +0000 (UTC)
From: "Igor Kabiljo (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12674419.1382048419561.31.1382673090951@arcas>
In-Reply-To: <JIRA.12674419.1382048419561@arcas>
References: <JIRA.12674419.1382048419561@arcas>
Subject: [jira] [Commented] (GIRAPH-785) Improve GraphPartitionerFactory
 usage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Igor Kabiljo commented on GIRAPH-785:
-------------------------------------

https://reviews.apache.org/r/14921/

> Improve GraphPartitionerFactory usage 
> --------------------------------------
>
>                 Key: GIRAPH-785
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-785
>             Project: Giraph
>          Issue Type: Improvement
>          Components: graph
>    Affects Versions: 1.1.0
>            Reporter: Igor Kabiljo
>            Priority: Minor
>         Attachments: partition_patch.txt
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Usage of GraphPartitionerFactory can be improved:
> - defining custom partitioner needs extending 3 classes/interfaces, and defining multiple functions, which is more complex than needed 
> - range partitioners are randomly assigning excess, instead of having each partition/worker having 1 consecutive range
> - if maxPartitions is reached, we might be creating number of partitions that is not divisible with number of workers


--
This message was sent by Atlassian JIRA
(v6.1#6144)