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 longer than the task execution time.
@squito it looks like you added this metric -- do you have a use case for
it?
cc @shivaram -- I know you've looked at the shuffle performance a lot so
chime in here if this metric has turned out to be useful for you!
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kayousterhout/spark-1 remove_fetch_variable
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/62.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #62
----
commit 43341ebed07971ccfa5ff0295cb4f6c5ab025403
Author: Kay Ousterhout <kayousterh...@gmail.com>
Date: 2014-03-03T03:37:55Z
Remote 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 longer than the task execution time.
----
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
