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.

Sign up for GitHub

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

Jump to bottom

Strided: Analyze overhead of strided datatype creation and decoding #34

Open
6 tasks
minsii opened this issue May 14, 2020 · 0 comments
Open
6 tasks

Strided: Analyze overhead of strided datatype creation and decoding #34

minsii opened this issue May 14, 2020 · 0 comments
Labels
TODO-evaluation
Projects
OpenSHMEM FY21 milestones
Milestone
FY21-Q3Q4

Comments

@minsii
Copy link
Collaborator

minsii commented May 14, 2020 •
edited

Description: Analyze overheads of strided datatype creation and decoding in the strided RMA path. Need to configure with --disable-strided-cache to disable the datatype cache optimization in OSHMPI.

Starting point:

  • Look into OSHMPI_create_strided_dtype function in OSHMPI.
  • Can use tests/iput.c as test program.

Hints: The datatype created in OSHMPI is always a resized vector with blocklength=1.

Evaluation platform: LCRC/Bebop Broadwell and KNL are preferred

Estimated effort: 3days - 1 week

TODOs:

  • Overhead breakdown of strided datatype creation in OSHMPI/MPICH/Yaksa path on CPU
  • Overhead breakdown of strided datatype creation in OSHMPI/MPICH/dataloop path on CPU (optional)
  • Overhead analysis of strided datatype decoding in PUT in OSHMPI/MPICH path (assume yaksa and dataloop are the same) on CPU
  • Overhead breakdown of strided datatype creation in OSHMPI/MPICH/Yaksa path on KNL
  • Overhead breakdown of strided datatype creation in OSHMPI/MPICH/dataloop path on KNL (optional)
  • Overhead analysis of strided datatype decoding in PUT in OSHMPI/MPICH path (assume yaksa and dataloop are the same) on KNL
@minsii minsii created this issue from a note in OpenSHMEM FY21 milestones (RMA analysis) May 14, 2020
@minsii minsii added this to the FY20-Q1Q2 milestone May 14, 2020
@minsii minsii modified the milestones: FY20-Q1Q2, FY21 Nov 6, 2020
@minsii minsii moved this from RMA analysis to Strided datatype analysis in OpenSHMEM FY21 milestones Feb 25, 2021
@minsii minsii changed the title Simple strided datatype optimization Strided: analysis overhead of strided datatype creation and decoding Feb 25, 2021
@minsii minsii changed the title Strided: analysis overhead of strided datatype creation and decoding Strided: Analysis overhead of strided datatype creation and decoding Feb 25, 2021
@minsii minsii changed the title Strided: Analysis overhead of strided datatype creation and decoding Strided: Analyze overhead of strided datatype creation and decoding Feb 25, 2021
@minsii minsii mentioned this issue Feb 25, 2021
Open
@minsii minsii modified the milestones: FY21-Q1Q2, FY21-Q3Q4 Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
TODO-evaluation
Projects
OpenSHMEM FY21 milestones
Strided datatype analysis
Milestone
FY21-Q3Q4
Development

No branches or pull requests
1 participant
@minsii