Unfortunately, I don't think there is an option then that will precisely do what you are asking then. Perhaps if you clarify more about what you are looking to test someone can help you approximate it better. Some suggestions though for you to look into: * Use a randrw process with percentage_random set to an appropriate value to control roughly how many blocks would be read before seeking. * Also a randrw process with bssplit set to a mix of small and large blocks sizes would make "random" IO intermittently more sequential. Daniel On Wed, Jul 8, 2015 at 11:08 PM, john gong <johngong0791@xxxxxxxxx> wrote: > hi Daniel, > > Thanks for your suggestion. > > "stonewall" can not solve my problem. "stonewall" just enforce the > processes which do the exact jobs run sequentially. > But what I want to do is that all things be done in one process, not > with one jobfile. > > B.R. > > On Thu, Jul 9, 2015 at 1:21 PM, danielabuggie . <danielabuggie@xxxxxxxxx> wrote: >> So you want to run them all with one jobfile, but sequentially and not >> simultaneously? >> >> In that case, stonewall is the option you want to add. >> >> Daniel >> >> On Wed, Jul 8, 2015 at 9:02 PM, john gong <johngong0791@xxxxxxxxx> wrote: >>> hello Kulkarni & Alireza, >>> >>> Thanks for your attentions. >>> tiobench-example.fio will spawn 16 processes, each job consumes 4 processes. >>> But what i want is all things defined in the job description be done >>> in one process. >>> For example, executes below job description >>> --cut-- >>> [global] >>> engine=sync >>> filename=/data/test >>> size=100m >>> [job1] >>> rw=write >>> stonewall >>> [job2] >>> rw=read >>> stonewall >>> [job3] >>> rw=randwrite >>> stonewall >>> [job4] >>> rw=randread >>> stonewall >>> --cut-- >>> >>> This job description can satisfy the demand of sequential execute, but >>> they will be done in 4 different processes. >>> What i want is all things be done in the same process sequentilly. >>> >>> B.R. >>> >>> John.Gong >>> >>> >>> >>> >>> >>> >>> On Thu, Jul 9, 2015 at 11:19 AM, Kulkarni, Vasu <vasu.kulkarni@xxxxxxxxx> wrote: >>>> Here's one example with 4 jobs which you can customize >>>> https://github.com/axboe/fio/blob/master/examples/tiobench-example.fio >>>> >>>> >>>> On Wed, Jul 8, 2015 at 6:55 PM, john gong <johngong0791@xxxxxxxxx> wrote: >>>>> hello All, >>>>> >>>>> I wonder whether FIO can do below things in the same job? >>>>> 1) sequential write >>>>> 2) sequential read >>>>> 3) randomly write >>>>> 4) randomly read >>>>> >>>>> Namely FIO do not need to spawn other processes to do the things respectively. >>>>> All things will be done in the same process. >>>>> >>>>> Thanks in advance! >>>>> >>>>> John.Gong >>>>> -- >>>>> 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 >>>> >>>> >>>> >>>> -- >>>> A ship is safer in a harbor. But that's not what ships are built for. >>> -- >>> 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 -- 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
