I think we should start a repository and update there, we can have optimum parameters per site also.
The BW of IOR are located in ior_$JOBID with details, for example:
Bandwidth 1 is 774570.92 MB/s and duration is 17.30 seconds
Bandwidth 2 is 123680.01 MB/s and duration is 7.78 seconds
Bandwidth 3 is 1250231.51 MB/s and duration is 10.72 seconds
Bandwidth 4 is 83650.59 MB/s and duration is 11.51 seconds
and the mdtests in the file mdt_$JOBID.
The script is prepared with SLURM commands and in this example I have used 2048 compute nodes, so feel free to adapt.
In case that we use Lustre, we need to run the experiment on another striped folder. Even for BB, I need to increase the MPI I/O aggregators in the case of shared file, but at least we have a first version for now.
See you at BOF.
Best regards,
George
________________________________________
KAUST Supercomputing Laboratory (KSL)
King Abdullah University of Science & Technology
Al Khawarizmi Bldg. (1) Room 0123
Thuwal
Kingdom of Saudi Arabia
Mob: +966 56 325 9012
Somehow the mail from John did not get through, so here it is (if there is an email issue please mail me). Thanks also for all those, we had discussions with, besides the Dagstuhl meeting...
All,
Sorry for the long silence on the mailing list. However, we have made some substantial progress recently as we prepare for our ISC BOF next week. For those of you at ISC, please join us from 11 to 12 on Tuesday in Substanz 1&2.
The progress that we have made recently happened because a bunch of us were attending a German workshop last month at Dagstuhl and had multiple discussions about the benchmark.
Here’s the highlights from what was discussed and the progress that we made at Dagstuhl:
-
General agreement that the IOR-hard, IOR-easy, mdtest-hard, mdtest-easy approach is appropriate.
-
We should add a ‘find’ command as this is a popular and important workload.
-
The multiple bandwidth measurements should be combined via geometric mean into one bandwidth.
-
The multiple IOPs measurements should also be combined via geometric mean into one IOPs.
-
The bandwidth and the IOPs should be multiplied to create one final score.
-
The ranking uses that final score but the webpage can be sorted using other metrics.
-
The webpage should allow filtering as well so, for example, people can look at only the HDD results.
-
We should separate the write/create phases from the read/stat phases to help ensure that caching is avoided
-
Nathan Hjelm volunteered to combine the mdtest and IOR benchmarks into one git repo and has now done so. This removes the #ifdef mess from mdtest and now they both share the nice modular IOR backend
So the top-level summary of the benchmark in pseudo-code has become:
bw1 = ior_easy -write [user supplies their own parameters maximizing data writes that can be done in 5 minutes]
md1 = md_test_easy -create [user supplies their own parameters maximizing file creates that can be done in 5 minutes]
bw2 = ior_hard -write [we supply parameters: unaligned strided into single shared file]
md2 = md_test_hard -create [we supply parameters: creates of 3900 byte files into single shared directory]
bw3 = ior_easy -read [cross-node read of everything that was written in bw1]
md3 = md_test_easy -stat [cross-node stat of everything that was created in md1]
md5 = [we supply parameters to find a subset of the files that were created in the tests]
bw = geo_mean( bw1 bw2 bw3 bw4)
md = geo_mean( md1 md2 md3 md4 bd5)
Now we are moving on to precisely define what the parameters should look like for the hard tests and to create a standard so that people can start running it on their systems. By doing so, we will define the formal process so we can actually make this an official
benchmark. Please see the attached file in which we’ve started precisely defining these parameters. Let’s start iterating please on this file to get these parameters correct.