Closed eksklawa closed 3 years ago
Well, I can tell you that I never tested IO depths higher than 64.
I will take a look.
Maybe I’m out off the loop regarding the current state of SSDs, but those ‘crazy’ high iodepths, do they make sense?
Would you mind putting the json files in a zip for me and attach it to this issue? Then I can test for you.
I have attached whole output folder in zip file
I have added some instructions. The default maximum iodepth is 64 and that collided with the higher iodepths. This is now shown in an error message instead of a stack trace that doesn't help much.
I also think a 2D graph is more usefull for you as numjobs is just 1 for all results. Hope it helps.
I did run bench_fio command:
~/fio-plot/benchmark_script/bench_fio --target /tmp/testdir --type directory --mode randread randwrite --output . --iodepth 1 2 4 8 16 32 64 128 256 512 1024 2048 --numjobs 1 -s 20M -j ~/fio-plot/benchmark_script/fio-job-template.fio
which produced folder with logs and json files:
However when I run fio_plot command:
or
~/fio-plot/fio_plot/fio_plot -i ./testdir/4k/ -T "TESTRUN" -L -t iops -r randread
it produces only graph for iodepths 1-64
I found it fails on iodepth higher than 64
Am I doing/using something wrong?
temp.zip