Uh oh!
There was an error while loading. Please reload this page.
[SPARK-11496][GRAPHX] Parallel implementation of personalized pagerank - #9457
[SPARK-11496][GRAPHX] Parallel implementation of personalized pagerank#9457moustaki wants to merge 6 commits into
Conversation
dbtsai
commented
Nov 4, 2015
Jenkins, test this please |
SparkQA
commented
Nov 4, 2015
Test build #44990 has finished for PR 9457 at commit
|
moustaki
commented
Nov 4, 2015
Jenkins, test this please |
dbtsai
commented
Nov 4, 2015
Jenkins, add to whitelist |
SparkQA
commented
Nov 4, 2015
Test build #45033 has finished for PR 9457 at commit
|
There was a problem hiding this comment.
Since mllib depneds on graphx, please remove the breeze dependencies in mllib.
dbtsai
commented
Nov 4, 2015
Is return type I'm working on refactoring out the basic type in mllib into separate package, but this will not happen soon. (will likely happen in 1.7). |
moustaki
commented
Nov 7, 2015
Thanks for all the comments @dbtsai. I'll go through your various comments soon. About your last one, what would you recommend for the time being? |
dbtsai
commented
Nov 8, 2015
@moustaki For the sparse vector issue, we can wait for the change in spark 1.7 since this PR will not be in 1.6. Thanks. |
moustaki
commented
Nov 24, 2015
@dbtsai Just went through all your comments. Thanks a lot for the feedback! |
SparkQA
commented
Nov 24, 2015
Test build #46574 has finished for PR 9457 at commit
|
dbtsai
commented
Nov 24, 2015
@moustaki This PR looks good to me. I'll start to work on refactoring the mllib vector out after 1.6 release, so graphx can use those data structure. Then we can change BSV to mllib sparse vector implementation. Thanks. |
moustaki
commented
Nov 24, 2015
@dbtsai Sounds good - do you want to hold off merging in the meantime? |
dbtsai
commented
Nov 24, 2015
@moustaki yes, we need to hold off now until 1.7 window. |
rxin
commented
Jun 15, 2016
Thanks for the pull request. I'm going through a list of pull requests to cut them down since the sheer number is breaking some of the tooling we have. Due to lack of activity on this pull request, I'm going to push a commit to close it. Feel free to reopen it or create a new one. |
moustaki
commented
Jun 15, 2016
Sounds good. @dbtsai Let me know when your mllib vector refactor is out and I'll re-open this PR. |
dbtsai
commented
Jul 4, 2016
Hello @moustaki , The work of having standalone vectors and matrices had been done in SPARK-13944, and what you need to do is adding the dependency of Thanks. |
moustaki
commented
Jul 24, 2016
Thanks @dbtsai! |
(Updated version of [PR-9457](#9457), rebased on latest Spark master, and using mllib-local). This implements a parallel version of personalized pagerank, which runs all propagations for a list of source vertices in parallel. I ran a few benchmarks on the full [DBpedia](http://dbpedia.org/) graph. When running personalized pagerank for only one source node, the existing implementation is twice as fast as the parallel one (because of the SparseVector overhead). However for 10 source nodes, the parallel implementation is four times as fast. When increasing the number of source nodes, this difference becomes even greater.  Author: Yves Raimond <yraimond@netflix.com> Closes#14998 from moustaki/parallel-ppr.
(Updated version of [PR-9457](apache#9457), rebased on latest Spark master, and using mllib-local). This implements a parallel version of personalized pagerank, which runs all propagations for a list of source vertices in parallel. I ran a few benchmarks on the full [DBpedia](http://dbpedia.org/) graph. When running personalized pagerank for only one source node, the existing implementation is twice as fast as the parallel one (because of the SparseVector overhead). However for 10 source nodes, the parallel implementation is four times as fast. When increasing the number of source nodes, this difference becomes even greater.  Author: Yves Raimond <yraimond@netflix.com> Closesapache#14998 from moustaki/parallel-ppr.
makalaaneesh
commented
Mar 2, 2017
@moustaki Hey, I am currently working on a project that requires to perform PersonalizedPageRanks in parallel. Has this been merged, cause I can't find official documentation on this. |
moustaki
commented
Mar 3, 2017
@makalaaneesh Yes, it has been superseeded by another PR #9457 and merged. It's available in 2.1. |
This implements a parallel version of personalized pagerank, which runs all propagations for a list of source vertices in parallel.
I ran a few benchmarks on the full DBpedia graph. When running personalized pagerank for only one source node, the existing implementation is twice as fast as the parallel one (because of the SparseVector overhead). However for 10 source nodes, the parallel implementation is four times as fast. When increasing the number of source nodes, this difference becomes even greater.