User Tools

Site Tools


Submission Rules

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.

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.

  1. 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.
    1. $ git clone https://github.com/VI4IO/io500-app.git -b io500-isc20
    2. 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.
  2. 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.
    1. All create/write phases must run for at least 300 seconds; the stonewall flag must be set to 300 which should ensure this.
      1. We defined a very high workload for all benchmarks that should satisfy this requirement but you may have to set higher values.
      2. There can be no edits made to the source code including used codes such as IOR.
  3. The file names for the mdtest output files may not be pre-created.
  4. You must run all phases of the benchmark on a single storage system without interruption.
  5. All data must be written to persistent storage within the measured time for the individual benchmark, e.g. if a file system caches data, it must ensure that data is persistently stored before acknowledging the close.
  6. 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.
  7. 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.
    1. It is not required to capture the list of matched files.
  8. Please also refer to the README documents in the GitHub repo.
  9. Please read the CHANGELOG.md file for the new changes on the IO-500 benchmark
  10. Only submissions using at least 10 physical client nodes are eligible to win IO500 awards and at least one benchmark process must run on each
    1. We accept results on fewer nodes for documentation purposes but they cannot be awarded.
    2. Virtual machines can be used but the above rule must be followed. More than one virtual machine can be run on each physical node.
    3. For the 10 node challenge, there must be exactly 10 physical nodes and at least one benchmark process must run on each
    4. The only exception to this rule is the find benchmark which may optionally use fewer nodes/processes
  11. 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.