-
Notifications
You must be signed in to change notification settings - Fork 265
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
added parallel I/O bench-marking program that mimics NOAA UFS data writing from the FV3 #1785
Merged
Conversation
This file contains 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
…n-parallel builds
Merged
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.
Fixes #1771
Fixes #1770
Part of #1543
Part of #1710
This PR adds a benchmark/test program tst_gfs_data_1.c in the nc_perf directory. The test builds a file just like one output by NOAAs GFS code. It then writes some data to the file, just as NOAA does.
This is similar to the test recently merged to netcdf-fortran (Unidata/netcdf-fortran#265). However, the C test does timing of various choices (for example, compression level and use of shuffle).
See the netcdf-fortran issue for detailed description of the file contents.
The intent is to have a test that uses netCDF just like the NOAA FV3 code, but also allows us to time various choices to see what performs best.
The extra test is only build when --enable-benchmarks is used, for parallel I/O builds.