Skip to content

Conversation

@tvegas1
Copy link
Contributor

@tvegas1 tvegas1 commented Oct 10, 2023

cherry-pick: #11893

At very high scale, having each rank storing each other rank's remote keys for
each segment can lead to high memory consumption.

We activate symmetric remote key option to generate remote keys that will be
deduplicated and then used interchangeably.

Signed-off-by: Thomas Vegas [email protected]

@github-actions github-actions bot added this to the v4.1.7 milestone Oct 10, 2023
@tvegas1
Copy link
Contributor Author

tvegas1 commented Oct 10, 2023

retested de-duplication with 30 segs

Copy link
Contributor

@yosefe yosefe left a comment

Choose a reason for hiding this comment

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

pls squash

At very high scale, having each rank storing each other rank's remote keys for
each segment can lead to high memory consumption.

We activate symmetric remote key option to generate remote keys that will be
deduplicated and then used interchangeably.

Signed-off-by: Thomas Vegas <[email protected]>
(cherry picked from commit 776e8ba)
@tvegas1 tvegas1 force-pushed the smkey_store_v4.1.x branch from 6a7dcba to 937abaf Compare October 11, 2023 07:39
@bwbarrett bwbarrett merged commit 386b88d into open-mpi:v4.1.x Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants