Github user squito commented on the pull request:
https://github.com/apache/spark/pull/62#issuecomment-36589314
I think I just threw a bunch of different metrics together, I don't think
this one was ever that useful. It would be nice to have something to measure
bandwidth, but I gues
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 enable
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 not
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/62#issuecomment-36575370
LGTM
---
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
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 appe
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/62#issuecomment-36483058
Unfortunately this isn't very useful for getting network bandwidth...if you
consider a simple case where two shuffle reads (for one task) occur
simultaneously a
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 i
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 t
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 shuffl
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 th
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 have
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 longe
12 matches
Mail list logo
