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

ATM: Runtime memory increases associated w/NetCDF reads #2438

Open
LarissaReames-NOAA opened this issue Sep 12, 2024 · 0 comments
Open

ATM: Runtime memory increases associated w/NetCDF reads #2438

LarissaReames-NOAA opened this issue Sep 12, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@LarissaReames-NOAA
Copy link

Description

When running ATM in either global or regional mode PET VMPeak (as output by the ProfileMemory=true setting in ufs.configure) jumps up each time a LBC file is read (in regional) or a climatological file is read (for global runs). We do not see similar memory increases for other model components when run in coupled mode (S2S).

To Reproduce:

  1. Compile with current develop branch (or anything back to at least #45c8b2a) using either intel or GNU on either Hera or Jet
  2. Run either control_c48 or regional_control regression test with ProfileMemory = true in ufs.configure
  3. Output VMPeak values increase in large jumps around the time LBCs/Climo files are read in

Additional context

This behavior was revealed by @DeniseWorthen when investigating Issue #2320 . It's not clear that these memory issues are the direct cause of the long run failures reported there given that they are evident when the reported "working" #45c8b2a is used.

Output

Memory profile traces of select PETs from both global and regional runs for reference. These were all produced on Hera but runs on Jet produce similar results.

With intel/2021.5.0
regional_mem
c48_mem

With intel/2023.2.0

regional_mem_intel2023
c48_mem_intel2023

@LarissaReames-NOAA LarissaReames-NOAA added the bug Something isn't working label Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant