Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add nsys profiling to coupler #700

Open
Tracked by #2943
juliasloan25 opened this issue Mar 18, 2024 · 1 comment · May be fixed by #701
Open
Tracked by #2943

Add nsys profiling to coupler #700

juliasloan25 opened this issue Mar 18, 2024 · 1 comment · May be fixed by #701
Assignees
Labels
GPU 🍃 leaf Issue coupled to a PR

Comments

@juliasloan25
Copy link
Member

Add nsys profiling for representative runs of our different coupler configurations. Use this information to identify improvements we need to make to the coupler

runs to consider:

  • target AMIP (diagnostic EDMF + topography)
  • DYAMOND AMIP
  • slabplanet (with static albedo)
@Sbozzolo
Copy link
Member

nsys gives you very detailed information, but it harder to use and interpret. I think that at this stage, a flame graph would be a more direct way to identify what is going wrong. Most likely, there are large allocations somewhere, and we just need to identify where. You can just run for one coupled cycle for the flamegraph instead of instrumenting a multi-hour run.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
GPU 🍃 leaf Issue coupled to a PR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants