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

Add learning objectives for HPC Scalability Profiling #87

Open
steve-crouch opened this issue Apr 26, 2024 · 0 comments
Open

Add learning objectives for HPC Scalability Profiling #87

steve-crouch opened this issue Apr 26, 2024 · 0 comments
Labels
oxford-hackathon This can be worked on during the Oxford Hackathon on 29 April 2024.

Comments

@steve-crouch
Copy link
Contributor

steve-crouch commented Apr 26, 2024

There are no learning objectives for the HPC Scalability Profiing lesson, although they do already exist for the original materials upon which they are based. A suggested ported set of learning objectives (curated to what's in the UNIVERSE-HPC version) are:

  • Understanding Code Scalability
    • Describe why code scalability is important when using HPC resources.
    • Explain the difference between wall time and CPU time.
    • Describe the differences between strong and weak scaling.
    • Summarise the dangers of premature optimisation.
  • Scalability Profiling
    • Explain how Amdahl’s Law can help us understand the scalability of code.
    • Use Amdahl’s Law to predict the theoretical maximum speedup on some example code when using multiple processors.
    • Understand strong and weak scaling graphs for some example code.
    • Describe the graphing characteristics of good and bad scalability.
@steve-crouch steve-crouch added the oxford-hackathon This can be worked on during the Oxford Hackathon on 29 April 2024. label Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
oxford-hackathon This can be worked on during the Oxford Hackathon on 29 April 2024.
Projects
None yet
Development

No branches or pull requests

1 participant