On 15 January 2016 at 16:09, Dallas Clement <dallas.a.clement@xxxxxxxxx> wrote: > > I suspected that might be the case. Is this dirty memory on the > client side where fio is running or on the target host where the data > has been written to? It will be on the client side - you aren't waiting for anything to flush so it can even just queue in the kernel's page cache. > I would like to make fio sync in a similar fashion to what real > applications would do. Setting sync=1 is probably too aggressive. > Probably a sync after a given number of blocks would seem more > realistic. Try taking a look at the fsync parameter in the HOWTO: https://github.com/axboe/fio/blob/fio-2.3/HOWTO#L909 . -- Sitsofe | http://sucs.org/~sits/ -- 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
