The benchmark script is tailored to fio-plot and knows about this limitation. This means that for each job/test a separate JSON file is generated with just one job.
Using the fio configuration file, it is possible to run many different jobs in one benchmark run. This is not supported by the benchmark script nor fio-plot.
At this point it is not clear how much of a problem this really is and how much effort would be required to handle the multiple jobs.
The internal code is also not aware of jobs and this would probably touch a ton of of code.
The benchmark script is tailored to fio-plot and knows about this limitation. This means that for each job/test a separate JSON file is generated with just one job.
Using the fio configuration file, it is possible to run many different jobs in one benchmark run. This is not supported by the benchmark script nor fio-plot.
At this point it is not clear how much of a problem this really is and how much effort would be required to handle the multiple jobs. The internal code is also not aware of jobs and this would probably touch a ton of of code.