This email serves to inform you that a finalized ISC19 IO500 list has been
released. The difference between this list and the one announced last week
at ISC is that the committee discovered that two submissions were passing
the '-u' flag to mdtest hard. This flag causes mdtest to create a
subdirectory for each process and therefore causes submissions to be
noncompliant with our rules as previously described in the README and now
clarified on a page by itself. As always, our lists can be seen at
IO500 Board (George, Jay, John, Julian)
I somehow expect this to be outside the spirit of the IO-500 benchmark
but though it worth checking:
Is there any scope for using different filesystem targets for the
different tests in the IO-500 benchmark suite, whilst still using the
same underlying storage hardware? i.e. have a filesystem configured in
one way for the mdtest parts and another filesystem on the same hardware
for the IOR parts?
Currently the script only allows the specification of a single working
directory (io500_workdir), so without changing the setup to incorporate
different working directories (which looks like it's forbidden under the
current rules) it's not possible at the moment. To enable such an
approach multiple working directories would have to be defined/available....
Tel: +44 131 6506470 skype: remoteadrianj
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.