On Thu, Jun 27 2013, Roger Sibert wrote:
> Just a thought that came to mind.
>
> To work around the problem would the following work?
> Run fio to get you max MB/s
> Write a script to generate you work/jobs file that has randomizes
> length of time for the job to run and % of max for it to run at.
That's a bit of a bother, though, since you have to collect data and
output from each individual run. And not only that, shutdown/startup
will make things less than smooth. It could potentially dirty your
results.
We could have something ala:
rate_sequence={10s:20M},{20s:5M}
or whatever, which runs 10s at 20M/sec, then 20s at 5M/sec. Repeat.
Would be fairly easy to do.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
