Issues with read_iolog trace replay

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I am trying to simulate bursty traffic with fo.  I know that I can do
this by tracing a bursty app and then doing a blktrace replay, but I
would like to do something programatic.

I had hoped that I could create an io_replay file that looks like this
which would read, then pause for 100ms before issuing the next read.
Once working I could then vary (lower) the "wait" period to generate
the bursts.

But what seems to happen is that all the "wait" lines are executed
sequentially, followed by all the "reads" sequentially, without the
100ms pause in-between.

FWIW, using blktrace input works as expected, and replays the trace at
the same iO rate as the traced workload.

[root@arches filebench]# /usr/local/bin/fio --version
fio-3.13

[root@arches filebench]# /usr/local/bin/fio --name=replay
--read_iolog=read100.csv

[gary@arches filebench]$ cat read100.csv
fio version 2 iolog
/dev/sdc add
/dev/sdc open
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc read 16384 4096
/dev/sdc wait 100000 1
/dev/sdc close



[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux