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

[FEA] Add experimental multi-threaded BypassMergeSortShuffleWriter #6060

Closed
abellina opened this issue Jul 22, 2022 · 0 comments · Fixed by #6052
Closed

[FEA] Add experimental multi-threaded BypassMergeSortShuffleWriter #6060

abellina opened this issue Jul 22, 2022 · 0 comments · Fixed by #6052
Assignees
Labels
feature request New feature or request P1 Nice to have for release performance A performance related task/issue shuffle things that impact the shuffle plugin

Comments

@abellina
Copy link
Collaborator

This is a part of: #5039

This task is to add an experimental multi-threaded writer to handle compression and the IO required for writing shuffle blocks on the CPU. We have noticed that writing these blocks to temporary (map_id, reducer_id) files is CPU-bound in the lz4 case, and so adding more threads is beneficial for shuffle-intensive queries.

@abellina abellina added feature request New feature or request shuffle things that impact the shuffle plugin P1 Nice to have for release labels Jul 22, 2022
@abellina abellina added this to the Jul 11 - Jul 22 milestone Jul 22, 2022
@abellina abellina self-assigned this Jul 22, 2022
@abellina abellina added the performance A performance related task/issue label Jul 22, 2022
@abellina abellina changed the title [FEA] Add experimental multi-threaded shuffle writer [FEA] Add experimental multi-threaded BypassMergeSortShuffleWriter Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request P1 Nice to have for release performance A performance related task/issue shuffle things that impact the shuffle plugin
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant