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

Avoid more comm/compute overlap in ugni #15193

Merged
merged 1 commit into from
Mar 16, 2020

Conversation

ronawho
Copy link
Contributor

@ronawho ronawho commented Mar 12, 2020

In #12964 we eliminated comm/compute overlap for FMA operations when a
task hadn't done ~100 FMA operations. Here we extend that to RDMA and
chained FMA operations as well. This is motivated by aggregation work
where we do on-stmts followed by large RDMA PUTs/GETs, but we really
don't want too many tasks started at once since that increases memory
pressure. This also adds an option to completely disable comm/compute
overlap in ugni, but it's not enabled by default since it has a 2x
performance hit for SSCA.

In 12960 we eliminated comm/compute overlap for FMA operations when a
task hadn't done ~100 FMA operations. Here we extend that to RDMA and
chained FMA operations as well. This is motivated by aggregation work
where we do on-stmts followed by large RDMA PUTs/GETs, but we really
don't want too many tasks started at once since that increses memory
presssure. This also adds an option to completely disable comm/compute
overlap in ugni, but it's not enabled by default since it has a 2x
performance hit for SSCA.
@ronawho ronawho requested a review from gbtitus March 12, 2020 19:31
@cassella

This comment has been minimized.

@ronawho

This comment has been minimized.

Copy link
Member

@gbtitus gbtitus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@ronawho ronawho merged commit 3549a18 into chapel-lang:master Mar 16, 2020
@ronawho ronawho deleted the avoid-comm-compute-overlap-ugni branch March 16, 2020 15:52
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