Repository navigation
Default to the WRF output and rank settings measured in #89 - #92
Merged
Merged
Conversation
aethr
added a commit
that referenced
this pull request
Oct 9, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Measured on aust10km, together these take wrf-run from 2 h 15 min to 1 h 9 min: - history_begin_h is set from the spin-up length, so wrf.exe no longer writes the spin-up output that cleanup deletes unread. - use_netcdf_classic, so the 5-minute frames are not compressed on rank 0 before being averaged and deleted. - debug_level = 0, which drops the trace lines written on every halo exchange. debug_level = 100 comes out of the domain namelists: these describe how we run wrf.exe, not the domain, so all three are set when the namelist is generated. - The default rank count is the number of physical cores, rather than every hardware thread. The first three leave the hourly output byte-identical. The rank count changes the decomposition, which changes the output at the level of rounding, as moving between hosts already does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 9, 2026
prayner
approved these changes
Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #89. Takes the four settings #89 measured to pay off and makes them the defaults, directly on
main. It replaces #91, and leaves out #90's experiment-only environment variables (namelist overrides, extrampirunarguments, quilting rank accounting), because the settings they tested either became defaults here or made no difference. Measured results are in #89 (comment).Changes
c8id.16xlarge)history_begin_h=num_hours_spin_upsetup_for_wrf.pyuse_netcdf_classic = .true.setup_for_wrf.pydebug_level = 0(was 100)setup_for_wrf.py; removed from everydomains/*/namelist.wrfsafe_mpi_tasks(), newphysical_cpu_count()Together:
wrf-run8,125 s → 4,163 s.Notes
wrf.exe, not the domain.history_begin_hfollows the config's spin-up length.physical_cpu_count()counts distinct(physical id, core id)pairs in/proc/cpuinfo. It falls back toos.cpu_count()where those fields are missing, as on aarch64, which has no SMT anyway.NCPUSstill overrides the default.WrfStorageSpothosts the default drops from 64 ranks to 32. A 96-vCPU host would get 48.wrf.exewrites.average_fields()still compresses the hourlyWRFOUTfiles.Testing
make test: passes, including new tests forphysical_cpu_count()(hyperthreaded, two-socket, no core information).🤖 Generated with Claude Code