Hey Glenn,
Looks like Andreas answered some of your questions. I'll answer a few more.
There is only one version of IO500. You can run it with or without stonewall and both are valid results. There are a few caveats:
- It only works right now with IOR and pfind and you must set a stonewall limit of at least 300 seconds
- It would be nice if it works with mdtest but that hasn't been added yet
- For IOR, you must use the --stoneWallingWearOut option so that stragglers are accounted for
- The io500.sh doesn't support it yet so you'd have to modify it.
- What it should do is automatically parse the output of the IOR write phases and record the actual amount of data written by each process and then pass those values to the corresponding read phase.
- One thing you can do is run it once with stonewall to see how much IO you can do in five minutes and then modify io500.sh accordingly.
- Obviously it will be better when io500.sh does this for us.
When you say anonymous, what exactly did you have in mind? Shroud institution, vendor, file system type, or just some of these? It's a tough balance. Obviously we want submissions but is there value in a totally anonymous result? I guess we see the degradation from easy to hard but is it useful information if we don't know what filesystem it was? Here's an example of something that would be awesome: someone submits a Lustre result with very little degradation from easy to hard and other people in the community say, "Wow! How did they do that?" and IO500 submission contains enough info for this result to be reproducible. An anonymous submission wouldn't allow this. Is there some other value it provides beyond just inflating the list? (which might be sufficiently valuable in and of itself . . .)
John