On Fri, Apr 05 2013, Michal Šmucr wrote: > Hello to all, > this is actually great thread. I discovered wonderful fio before two > days during seeking for tool, which allows me to simulate typical > workload with DPX files playback and recording (one file per frame). > I'm playing with it today and slowly getting into options. By > coincidence, i subscribed to this list to ask almost same question as > Alan and found this first thread.. :-) > Reusing of generated frames (file sequences) between write and read > jobs is also important for me and is exactly thing, what i thought > about. I will try to test patch by Jens. > > One small thing, sorry for slight derail of thread topic, which come > to my mind was option for kind of automatic set of blocksize during > read to match length of each pre-generated file within sequence, which > fio got from directory using opendir directive. Idea behind this come > from common behaviour of VFX applications, which issue read io for > whole frame size. So application use stat() output to get actual file > size before reading of each frame. If I have same filesize per frame > it is easy to adjust blocksize before benchmark, but if i want to test > read performance of sequence with compressed frames or simulate > mixture of different resolutions, this will be handy. It would not be a problem making the block size decision probed or dynamic. But it's not clear to me from the above what you would base it on. The file size? Or st_blksize? > Thank you and especially Jens for creation of fio (first day with it > is mindblowing :) You're welcome, glad you like it :-). Fio grows with great suggestions from people actually using it, which this thread is a good example of. -- 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
