From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 References: In-Reply-To: From: Sitsofe Wheeler Date: Thu, 18 Oct 2018 05:19:18 +0100 Message-ID: Subject: Re: FIO 3.11 Content-Type: text/plain; charset="UTF-8" To: "Elliott, Robert (Persistent Memory)" Cc: efortin@cyberspicace.com, fio , Jens Axboe List-ID: On Wed, 17 Oct 2018 at 22:45, Elliott, Robert (Persistent Memory) wrote: > > > These will make each thread implement your desired mix: > > rwmixread=int [...] > rwmixwrite=int [...] > percentage_random=int[,int][,int] [...] Another (but more overlooked) option for forcing different jobs into lockstep with each other is the flow parameter - https://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-flow but it tends to be easiest to reason about when there are just two jobs. > > Threads running sequential accesses can easily benefit from cache hits from each other, if > there is any caching or prefetching done by the involved drivers or devices. One thread > takes the lead and suffers delays, while the others benefit from its work and stay close > behind. They can take turns, but tend to stay clustered together. This can distort results. > Random accesses avoid that problem, provided the capacity is much larger than any caches. -- Sitsofe | http://sucs.org/~sits/