[
https://issues.apache.org/jira/browse/FLINK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353199#comment-14353199
]
Vasia Kalavri commented on FLINK-1536:
--------------------------------------
Hi [~ayd],
for more information on what your proposal should be like, take a look at the
[GSoC website|
https://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page#5._What_should_a_student_proposal_look].
Then, I would suggest you go through the literature I have posted in the issue
description.
This project isn't about implementing a particular partitioning algorithm. We
can actually try many things here, for example partition a graph at loading
time, efficient re-partitioning of a graph, re-using an already partitioned
graph, stream partitioning algorithms or other cool ideas we may come up with.
-Vasia.
> GSoC project: Graph partitioning operators for Gelly
> ----------------------------------------------------
>
> Key: FLINK-1536
> URL: https://issues.apache.org/jira/browse/FLINK-1536
> Project: Flink
> Issue Type: New Feature
> Components: Gelly, Java API
> Reporter: Vasia Kalavri
> Priority: Minor
> Labels: graph, gsoc2015, java
>
> Smart graph partitioning can significantly improve the performance and
> scalability of graph analysis applications. Depending on the computation
> pattern, a graph partitioning algorithm divides the graph into (maybe
> overlapping) subgraphs, optimizing some objective. For example, if
> communication is performed across graph edges, one might want to minimize the
> edges that cross from one partition to another.
> The problem of graph partitioning is a well studied problem and several
> algorithms have been proposed in the literature. The goal of this project
> would be to choose a few existing partitioning techniques and implement the
> corresponding graph partitioning operators for Gelly.
> Some related literature can be found [here|
> http://www.citeulike.org/user/vasiakalavri/tag/graph-partitioning].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
