>>>>> >>>>>Just to confirm.. >>>>> >>>>> bs_is_seq_rand=1 >>>>> >>>>> bs=64k,4k >>>>> >>>>> It's 64K for sequential and 4K for random >>>>> >>>>> Right? >>>> >>>> Correct. If bs_is_seq_rand is set, any READ block size setting is >>>> applied to sequential IO, and any WRITE block size setting is applied >>>>to >>>> random IO. >>>> >>>> -- >>>> Jens Axboe >>>> >>> >>> Let me see if I understood: >>> >>> But Jens, if I want sequential read AND write 64KB and random read AND >>> write 4KB? >> >>Then you'd do: >> >>bs=64k,4k >>bs_is_seq_rand=1 >> >>any ANY sequential IO will be 64kb, and ANY random IO will be 4kb. >> >>-- >>Jens Axboe >> > >This? > >[workload] >bs=64k,4k > >bs_is_seq_rand=1 > >ioengine=libaio >iodepth=2 >numjobs=64 >direct=1 >runtime=2400 >size=2000g >filename=\\.\PhysicalDrive9:\\.\PhysicalDrive10 >rw=randrw >rwmixread=85 >percentage_random=59,67 >thread >unified_rw_reporting=1 >group_reporting=1 Jens Would be nice if we could specify? Iodepth for sequential and random Numjobs for sequential and random (for example: I would like to have 16 jobs doing random and 1 job only doing sequential) Thanks for considering it in the future All the best my friend neto -- 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
