User Tools

Site Tools


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
Next revisionBoth sides next revision
io500:rules:submission [2019/09/23 16:19] john_bentio500:rules:submission [2019/11/09 14:32] – [Submission Rules] kunkel
Line 11: Line 11:
     - We defined a very high workload for all benchmarks that should satisfy this requirement but you may have to set higher values.     - 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 io-500.sh 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 script beyond changing the allowed variables and adding commands to configure the storage system (e.g. setting striping parameters).  
-    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/io500_fixed.sh scripts.  +    No edits are allowed to the utilities/io500_fixed.sh scripts.  
   - 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.
   - 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.   - 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.
-  - 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 [[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.
   - 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
   - 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
-    Virtual machines can be used but the above rule must be followed.  More than one virtual machine can be run on each physical node.+    Virtual machines can be used but the above rule must be followed.  More than one virtual machine can be run on each physical node.