|
|
# Running IO500 with GekkoFS
|
|
|
|
|
|
To run IO500, there are a few configuration options that need to be set for it to be run with GekkoFS. This includes defining `LD_PRELOAD`, other environment variables, or creating the experiment directories in GekkoFS beforehand.
|
|
|
|
|
|
IO500 can be run with GekkoFS either with `srun` or `mpirun/mpiexec` on the client side.
|
|
|
|
|
|
## Download and build IO500
|
|
|
|
|
|
There are usually dedicated branches for the calls for submission, e.g., `io500-isc20` for ISC 2020. Therefore, the following steps are needed to build IO500 on your system.
|
|
|
|
|
|
```
|
|
|
git clone https://github.com/VI4IO/io500-app.git -b io500-isc20
|
|
|
cd io500
|
|
|
./prepare.sh
|
|
|
```
|
|
|
Prepare will download and build IOR, MDtest, pfind, and IO500. IO500 offers a C-App which combines these three benchmarks.
|
|
|
Note: Sometimes there are issues building `pfind` because `mpicc` is not found. XXX
|
|
|
|
|
|
## Configuring IO500
|
|
|
|
|
|
When running IO500, you can add any file system settings that you need, e.g., env variables, to `io500.sh`. There will be a comment where you are not allowed to add anything thereafter. |
|
|
\ No newline at end of file |