[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2015-03-16 Thread ankurdave
Github user ankurdave commented on the pull request: https://github.com/apache/spark/pull/2679#issuecomment-81482998 This was mostly just a proof of concept since coarsening is something GraphX can do that other graph systems can't. Since I'm not sure there's really demand for it I'm

[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2015-03-16 Thread ankurdave
Github user ankurdave closed the pull request at: https://github.com/apache/spark/pull/2679 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2015-02-25 Thread nchammas
Github user nchammas commented on the pull request: https://github.com/apache/spark/pull/2679#issuecomment-76069522 @ankurdave This PR has gone stale. Were you waiting for feedback from someone? --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2014-10-14 Thread uncleGen
Github user uncleGen commented on the pull request: https://github.com/apache/spark/pull/2679#issuecomment-59037906 @ankurdave I see. And I think it is worthy to provide a memory-based shuffle manager in some cases, like sufficient memory resources, stringent performance requirement,

[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2014-10-13 Thread uncleGen
Github user uncleGen commented on the pull request: https://github.com/apache/spark/pull/2679#issuecomment-58885039 @ankurdave I have some doubts, but not about this patch. In [GraphX OSDI paper](http://ankurdave.com/dl/graphx-osdi14.pdf) , I find that you have implemented a

[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2014-10-13 Thread ankurdave
Github user ankurdave commented on the pull request: https://github.com/apache/spark/pull/2679#issuecomment-58939148 @uncleGen We implemented in-memory shuffle for benchmarking in 5ec645d945783457baed9e151337b2735c1b307f around the time of Spark 0.9.1 but didn't merge it back, and

[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2014-10-06 Thread ankurdave
GitHub user ankurdave opened a pull request: https://github.com/apache/spark/pull/2679 [SPARK-3818] Graph coarsening Listing 7 in the [GraphX OSDI paper](http://ankurdave.com/dl/graphx-osdi14.pdf) contains pseudocode for a coarsening operator that allows merging edges that satisfy

[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2014-10-06 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/2679#issuecomment-58047413 [QA tests have started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21334/consoleFull) for PR 2679 at commit

[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2014-10-06 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/2679#issuecomment-58059217 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: [SPARK-3818] Graph coarsening

2014-10-06 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/2679#issuecomment-58059198 [QA tests have finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21334/consoleFull) for PR 2679 at commit