... | ... | @@ -58,4 +58,40 @@ XXX @Ramon |
|
|
|
|
|
### io500 config
|
|
|
|
|
|
The next step is to set the general rules how io500 runs with regards to runtime, number of files for mdtest_easy, benchmark directory, etc. For an io500 run to be successful it must run 300 seconds per experiment. Most benchmark parameters are fixed, but others like ior_easy can be modified. Consult the config file for further info. Note, that the number of processes that are used is separately defined `[find]` section of config file. |
|
|
\ No newline at end of file |
|
|
The next step is to set the general rules how io500 runs with regards to runtime, number of files for mdtest_easy, benchmark directory, etc. For an io500 run to be successful it must run 300 seconds per experiment. Most benchmark parameters are fixed, but others like ior_easy can be modified. Consult the config file for further info. Note, that the number of processes that are used is separately defined `[find]` section of config file. Example file: [config-gkfs_full.ini](uploads/c040328e9bdb62bf7c97bf36e8393c00/config-gkfs_full.ini)
|
|
|
|
|
|
When io500 is run, you also need a `system-configuration.txt` file if it is supposed to be a valid submission. Place this file into the root directory of io500. You may modify the following example file to your needs: [system-information.txt](uploads/da716ef3be613547714e4e66d9bf1416/system-information.txt)
|
|
|
|
|
|
### GekkoFS configurations
|
|
|
|
|
|
Make sure to enable `gkfs::config::metadata::use_ctime` in the `config.hpp` which is required for the timestamp file that io500 is using.
|
|
|
|
|
|
Currently, the most standing issue is the readdir buffer holding all dentries during pfind. Therefore, modify `gkfs::config::rpc::dirents_buff_size` to `(2000 * 1024 * 1024)` which allows 2 GiB per process for dentries during pfind.
|
|
|
|
|
|
## Running io500
|
|
|
|
|
|
First start the daemons on all servers. Next start io500 via the following command `./io500.sh config-gkfs_full.ini`. Since all client hosts and process numbers have been defined in `io500.sh`, there are no further arguments required. The output then looks something like this:
|
|
|
|
|
|
```bash
|
|
|
vef@x0004 ~/vef_m2/io500 $ date && ./io500.sh config-gkfs_full.ini
|
|
|
Sat Oct 31 11:00:53 CET 2020
|
|
|
IO500 version io500-sc20
|
|
|
[RESULT] ior-easy-write 57.314222 GiB/s : time 369.921 seconds
|
|
|
[RESULT] mdtest-easy-write 2028.099784 kIOPS : time 390.588 seconds
|
|
|
[RESULT] ior-hard-write 18.790631 GiB/s : time 314.269 seconds
|
|
|
[RESULT] mdtest-hard-write 435.310912 kIOPS : time 324.130 seconds
|
|
|
[RESULT] find 4670.743390 kIOPS : time 198.140 seconds
|
|
|
[RESULT] ior-easy-read 27.161303 GiB/s : time 780.600 seconds
|
|
|
[RESULT] mdtest-easy-stat 2044.395443 kIOPS : time 384.341 seconds
|
|
|
[RESULT] ior-hard-read 6.367285 GiB/s : time 927.226 seconds
|
|
|
[RESULT] mdtest-hard-stat 1998.004349 kIOPS : time 69.947 seconds
|
|
|
[RESULT] mdtest-easy-delete 1909.283220 kIOPS : time 439.294 seconds
|
|
|
[RESULT] mdtest-hard-read 391.154105 kIOPS : time 357.341 seconds
|
|
|
[RESULT] mdtest-hard-delete 463.171214 kIOPS : time 302.176 seconds
|
|
|
[SCORE] Bandwidth 20.774337 GB/s : IOPS 1246.448969 kiops : TOTAL 160.916595
|
|
|
|
|
|
The result files are stored in the directory: ./results/2020.10.31-11.00.53
|
|
|
‘./io500.sh’ -> ‘./results/2020.10.31-11.00.53/io500.sh’
|
|
|
‘config-gkfs_full.ini’ -> ‘./results/2020.10.31-11.00.53/config-gkfs_full.ini’
|
|
|
Created result tarball ./results/io500-x0004.mogon-2020.10.31-11.00.53.tgz
|
|
|
``` |
|
|
\ No newline at end of file |