[GitHub] spark pull request: Remove the remoteFetchTime metric.

2014-03-03 Thread kayousterhout
Github user kayousterhout commented on the pull request: https://github.com/apache/spark/pull/62#issuecomment-36577709 I've merged this into master. --- 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

[GitHub] spark pull request: Remove the remoteFetchTime metric.

2014-03-03 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/62 --- 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: Remove the remoteFetchTime metric.

2014-03-02 Thread kayousterhout
GitHub user kayousterhout opened a pull request: https://github.com/apache/spark/pull/62 Remove the remoteFetchTime metric. This metric is confusing: it adds up all of the time to fetch shuffle inputs, but fetches often happen in parallel, so remoteFetchTime can be much

[GitHub] spark pull request: Remove the remoteFetchTime metric.

2014-03-02 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/62#issuecomment-36480711 Merged build triggered. --- 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

[GitHub] spark pull request: Remove the remoteFetchTime metric.

2014-03-02 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/62#issuecomment-36480712 Merged build started. --- 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

[GitHub] spark pull request: Remove the remoteFetchTime metric.

2014-03-02 Thread shivaram
Github user shivaram commented on the pull request: https://github.com/apache/spark/pull/62#issuecomment-36481963 Hmm -- I have been confused by this before, but if I am reading the comment right, this could be useful for to get an estimate of the raw network bandwidth used for

[GitHub] spark pull request: Remove the remoteFetchTime metric.

2014-03-02 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/62#issuecomment-36482478 All automated tests passed. Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12959/ --- If your project

[GitHub] spark pull request: Remove the remoteFetchTime metric.

2014-03-02 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/62#issuecomment-36482477 Merged build finished. --- 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

[GitHub] spark pull request: Remove the remoteFetchTime metric.

2014-03-02 Thread shivaram
Github user shivaram commented on the pull request: https://github.com/apache/spark/pull/62#issuecomment-36483177 Okay -- Thats seems like a separate conversation. This change looks good to me. --- If your project is set up for it, you can reply to this email and have your reply