Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| io500:rules:submission [2019/07/17 13:27] – [Submission Rules] john_bent | io500:rules:submission [2019/08/28 18:24] – [Submission Rules] kunkel | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| - The latest version of io500.sh in GitHub must be used and all binaries should be built according to the included build instructions. | - The latest version of io500.sh in GitHub must be used and all binaries should be built according to the included build instructions. | ||
| + | - $ git clone https:// | ||
| - All required phases must be run and in the same order as they appear in the io500.sh script. | - All required phases must be run and in the same order as they appear in the io500.sh script. | ||
| - Read-after-write semantics: The system must be able to correctly read freshly written data from a different client after the close operation on the writer has been completed. | - Read-after-write semantics: The system must be able to correctly read freshly written data from a different client after the close operation on the writer has been completed. | ||
| - | - All create phases should run for at least 300 seconds; the stonewall flag can be used as an optional convenience to help | + | - All create phases should run for at least 300 seconds; the stonewall flag must be set to 300 which should ensure this. |
| - | - For SC19: The stonewall flag must be used and must be set to 300. | + | - We defined a very high workload for all benchmarks that should satisfy this requirement but you may have to set higher values. |
| - | - There can be no edits made to the script beyond changing the allowed variables and adding commands to configure the storage system (e.g. setting striping parameters). | + | - There can be no edits made to the io-500.sh |
| * For example, there can be no artificial delays added within the script such as calling ‘sleep’ between phases. | * For example, there can be no artificial delays added within the script such as calling ‘sleep’ between phases. | ||
| * No edits are allowed to the utilities/ | * No edits are allowed to the utilities/ | ||
| - | * You may not overwrite any parameters that are set in utilities/ | ||
| - The file names for the mdtest and IOR output files may not be pre-created. | - The file names for the mdtest and IOR output files may not be pre-created. | ||
| - You must run the benchmark on a single storage system. | - You must run the benchmark on a single storage system. | ||
| - | - You must configure the batch scheduler to allocate the ranks in blocks, e.g. if you are running with five ranks per client node then rank 0-5 must be placed on Node0 and 6-10 on Node1. You should verify the appropriate placement. | ||
| - All data must be written to persistent storage within the measured time for the individual benchmark, | - All data must be written to persistent storage within the measured time for the individual benchmark, | ||
| - Submitting the results must be done in accordance with the instructions on our submission page. | - Submitting the results must be done in accordance with the instructions on our submission page. | ||
| - If a tool other than the included pfind is used for the find phase, then it must follow the same input and output behavior as the included pfind. | - If a tool other than the included pfind is used for the find phase, then it must follow the same input and output behavior as the included pfind. | ||
| - Please also refer to the [[https:// | - Please also refer to the [[https:// | ||
| - | + | - Please read the CHANGELOG.md file for the new changes on the IO-500 benchmark | |
| Please send any requests for changes to these rules or clarifying questions to our mailing list. | Please send any requests for changes to these rules or clarifying questions to our mailing list. | ||
