-
Notifications
You must be signed in to change notification settings - Fork 1
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
Large memory footprint when appending to an existing netCDF file #7
Comments
The issue is the way that the existing netCDF file is open when appending. The optional parameter specifies an override HDF5 cache size of 16GB. I suspect this was intended to be 16MB (the default is 1 MB). This occurs at nc_diag_write_mode.F90:326-327:
Excluding the FYI @aerorahul |
Testing has revealed that the GSI is using far too much memory when compiled with netCDF 4.9.2/gsi-ncdiag 1.1.1 and attempting to append to existing netCDF diagnostic files. For the global_4denvar test, this first shows up when the temperature operator setup function is called the second time. This tracks down to the ncdiag subroutine
nc_diag_init
withappend=.true.
. Running the test with just 12 PEs, the memory allocations suddenly jump from ~1.5GB/PE to ~6GB/PE. The exact function/subroutine called withinnc_diag_init
that causes this is still under investigation.The text was updated successfully, but these errors were encountered: