Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secondary Sort suggestion to reduce memory footprint at reducer #316

Merged
merged 1 commit into from
Jan 10, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions app/views/help/mapreduce/helpMemory.scala.html
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,8 @@ <h4>Suggestions</h4>
<br>
For example, see if there is any mapper/reducer input data skew (some task processes larger input than others).
<br>
Also check if you are doing memory intensive operation at reducer side for e.g. count distinct. These operations can be rewritten using Secondary Sort concept (sort the values), which will reduce the memory consumption
<br>
<strong>This is a new heuristic. We are still working on that. Any feedback is welcomed!</strong>
<br>

Expand Down