logo
Virtual Institute
for
I/O

User Tools

Site Tools

You are here: Virtual Institute for I/O » IO500 » Rules » Submission Rules

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
io500:rules:submission [2020/05/22 20:34] – ISC 20 rules publishing from approved Google doc gflofst_sandia.govio500:rules:submission [2020/08/13 17:09] – external edit 127.0.0.1
Line 3: Line 3:
 The following rules should ensure a fair comparison of the IO-500 results between systems and configurations. They serve to reduce mistakes and improve accuracy. The following rules should ensure a fair comparison of the IO-500 results between systems and configurations. They serve to reduce mistakes and improve accuracy.
  
- 0. For ISC20, submission of test runs should use new C-Application io500 which automatically runs both the new C version and the existing bash version (following the rules for SC-19) to ensure the consistency of results between the two implementations. An exception to this rule is possible for submitters who have a legitimate reason by requesting an exception from the committee via comittee@io500.org. +For ISC20, submission of test runs should use new C-Application io500 which automatically runs both the new C version and the existing bash version (following the rules for SC-19) to ensure the consistency of results between the two implementations. An exception to this rule is possible for submitters who have a legitimate reason by requesting an exception from the committee via comittee@io500.org. 
  
 Details are provided in the https://github.com/VI4IO/io500-app/blob/master/README-ISC20.txt file. For the ISC20 list, we will use the results from whichever of the two runs had the higher overall score assuming there are no abnormalities found in our analysis across all submissions.  Assuming no abnormalities are found, for future lists we will require only one run.   Details are provided in the https://github.com/VI4IO/io500-app/blob/master/README-ISC20.txt file. For the ISC20 list, we will use the results from whichever of the two runs had the higher overall score assuming there are no abnormalities found in our analysis across all submissions.  Assuming no abnormalities are found, for future lists we will require only one run.  
Line 9: Line 9:
   - Submissions are made using the latest version of the IO500 application in GitHub which runs both the existing bash version and the new C version and all binaries should be built according to the included build instructions.   - Submissions are made using the latest version of the IO500 application in GitHub which runs both the existing bash version and the new C version and all binaries should be built according to the included build instructions.
       - $ git clone https://github.com/VI4IO/io500-app.git -b io500-isc20       - $ git clone https://github.com/VI4IO/io500-app.git -b io500-isc20
-  - An exception to this rule is possible for submitters who have a legitimate reason by requesting an exception from the committee via comittee@io500.org. +      - An exception to this rule is possible for submitters who have a legitimate reason by requesting an exception from the committee via comittee@io500.org. 
   - Read-after-write semantics: The system must be able to correctly read freshly written data from a different client node 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 node after the close operation on the writer has been completed.
     - All create/write phases must run for at least 300 seconds; the stonewall flag must be set to 300 which should ensure this.     - All create/write phases must run for at least 300 seconds; the stonewall flag must be set to 300 which should ensure this.
Line 19: Line 19:
   - Submitting the results must be done in accordance with the instructions on our submission page. Please verify the correctness of your submission before you submit it.   - Submitting the results must be done in accordance with the instructions on our submission page. Please verify the correctness of your submission before you submit it.
   - 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 and the source code must be included in the submission.   - 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 and the source code must be included in the submission.
 +    - It is not required to capture the list of matched files.
   - Please also refer to the README documents in the GitHub repo.   - Please also refer to the README documents in the GitHub repo.
   - Please read the CHANGELOG.md file for the new changes on the IO-500 benchmark   - Please read the CHANGELOG.md file for the new changes on the IO-500 benchmark
Line 26: Line 27:
     - For the 10 node challenge, there must be exactly 10 physical nodes and at least one benchmark process must run on each     - For the 10 node challenge, there must be exactly 10 physical nodes and at least one benchmark process must run on each
     - The only exception to this rule is the find benchmark which may optionally use fewer nodes/processes     - The only exception to this rule is the find benchmark which may optionally use fewer nodes/processes
 +  - Each of the four main phases (IOR easy and hard, and mdtest easy and hard) has a subdirectory which can be precreated and tuned (e.g. using tools such as lfs_setstripe or beegfs_ctl); however, additional subdirectories within these subdirectories cannot be precreated.
  
 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.
Line 50: Line 52:
   - Submitting the results must be done in accordance with the instructions on our [[https://www.vi4io.org/io500-submission|submission page]].   - Submitting the results must be done in accordance with the instructions on our [[https://www.vi4io.org/io500-submission|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.
 +    - It is not required to capture the list of matched files.
   - Please also refer to the [[https://github.com/VI4IO/io-500-dev/blob/master/doc/README.md|README]] documents in the github repo.   - Please also refer to the [[https://github.com/VI4IO/io-500-dev/blob/master/doc/README.md|README]] documents in the github repo.
   - Please read the CHANGELOG.md file for the new changes on the IO-500 benchmark   - Please read the CHANGELOG.md file for the new changes on the IO-500 benchmark
io500/rules/submission.txt · Last modified: 2020/08/31 17:34 by kunkel
Impressum Privacy Driven by DokuWiki CC Attribution-Share Alike 4.0 International