2- To modify the codes-workload-test.conf file, change the 'workload_type' parameters. If using bgp_io_workload type, change the io_kernel_meta_path and bgp_config_file parameters according to your local path.
- workload_type is just the name of this generator ("bgp_io_workload")
- io_kernel_meta_path is the path to the i/o kernel meta file
- bgp_config_file is the path to the bgp config file
- rank_count is the number of ranks to generate i/o for
- this needs to match the range of ranks given in the io_kernel_meta_file
- this also needs to match the num_cn value in the bgp_config_file
- NOTE: num_ion should be set so there is 1 ion for every 64 cns
- NOTE: num_fileserver and num_es must be 64 or 123 (half or full storage system)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3.) darshan i/o workload generator:
PARAMS
{
workload_type = "darshan_io_workload";
log_file_path = "/path/to/darshan/log";
aggregator_count = "18";
}
3- Currently, the bgp_io_workload type only loads the workload file. TODO: read the operations inside the workload file one by one, load the appropriate parameters and display them correctly.
- workload_type is just the name of this generator ("darshan_io_workload")
- log_file_path is the path to the darshan log to generate i/o for
- aggregator_count is the number of collective aggregators to use for collective file i/o generation
- NOTE: this value may have a strong impact on the generated i/o pattern
- i.e. if it is not known, it may be very difficult to reproduce the original pattern
- NOTE: this value can be set to anything if the workload is mostly independently opened files