On Mon, Apr 08 2013, Michal Šmucr wrote: > 2013/4/5 Jens Axboe <axboe@xxxxxxxxx>: > > and then 'write' and 'read' job would be sharing those files. Let me > > know if it works for you. > > Thank you for patch Jens. > Re-using files working for me and i also like that string format > specification. Compiled with last git and tested on Mac OS X and > Centos 5. > I played with fio and sequence tests, it already helps me to get > figures much closer to real world utilization. I always struggled with > generic synthetic benchmarks as it usually don't work with sequences. > So i can roughly set IO sizes, modes, but for example can't simulate > performance differences caused by different file allocation between > one huge file (with few extents due to filesystem internal > optimization) and thousands of files. > Great! Thanks for testing and confirming that it both works and that the semantics make sense. I tagged 2.0.15 this morning and kept a few pending features/fixes in a 'next' branch, all have been pulled into the master branch. So the filename_format option is now in current -git, though it did not make 2.0.15 final. > P.S.: Here is what i tried as single thread HD video job. (and as > example where application read whole frame at once, so bs is > uncommonly equal filesize). > > [global] > ioengine=sync > buffered=0 > filesize=8305664 > bs=8305664 > nrfiles=3000 > openfiles=1 > filename_format=HD_sequence_test.$filenum.dpx > file_service_type=sequential > directory=/mnt/test/io > > [2min-sequence-write] > rw=write > > [2min-sequence-read] > stonewall > rw=read Looks sane! -- Jens Axboe -- 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
