Skip to content

Conversation

@zsxwing
Copy link
Member

@zsxwing zsxwing commented Aug 12, 2015

The peak execution memory is not correct because it shows the sum of finished tasks' values when a task finishes.

This PR fixes it by using the update value rather than the accumulator value.

@zsxwing
Copy link
Member Author

zsxwing commented Aug 12, 2015

/cc @davies @andrewor14

@SparkQA
Copy link

SparkQA commented Aug 12, 2015

Test build #40574 has finished for PR 8121 at commit 5a27802.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@andrewor14
Copy link
Contributor

Ah, we should display the partial update, not the partial accumulated value so far. LGTM merging into master 1.5.

asfgit pushed a commit that referenced this pull request Aug 12, 2015
The peak execution memory is not correct because it shows the sum of finished tasks' values when a task finishes.

This PR fixes it by using the update value rather than the accumulator value.

Author: zsxwing <zsxwing@gmail.com>

Closes #8121 from zsxwing/SPARK-9829.

(cherry picked from commit 4e3f4b9)
Signed-off-by: Andrew Or <andrew@databricks.com>
@asfgit asfgit closed this in 4e3f4b9 Aug 12, 2015
@zsxwing zsxwing deleted the SPARK-9829 branch August 13, 2015 12:28
CodingCat pushed a commit to CodingCat/spark that referenced this pull request Aug 17, 2015
The peak execution memory is not correct because it shows the sum of finished tasks' values when a task finishes.

This PR fixes it by using the update value rather than the accumulator value.

Author: zsxwing <zsxwing@gmail.com>

Closes apache#8121 from zsxwing/SPARK-9829.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants