When reading examples, many jobs assign a value to time_based.
It could even very misleading as some put the same value as for the runtime.
No value is expected, so let's have all examples using the same syntax.
Signed-off-by: Erwan Velu <e.velu@criteo.com>
16 files changed:
size=100g
rw=randread
norandommap
-time_based=0
+time_based
bs=2m
ioengine=dev-dax
norandommap
-time_based=1
+time_based
runtime=30
group_reporting
disable_lat=1
# Run e4defrag and aio-dio workers in parallel
[e4defrag]
stonewall
-time_based=30
+time_based
runtime=30
ioengine=e4defrag
buffered=0
bs=4k
donorname=file3.def
filename=file3
-time_based=30
+time_based
rw=randwrite
[buffered-aio-32k]
filename=file3
rw=randrw
runtime=30
-time_based=30
+time_based
numjobs=4
[direct-aio-32k]
filename=file3
rw=randrw
runtime=30
-time_based=30
numjobs=4
[falloc-fuzzer]
stonewall
runtime=10
-time_based=10
+time_based
bssplit=4k/10:64k/50:32k/40
rw=randwrite
numjobs=1
[punch hole-fuzzer]
bs=4k
runtime=10
-time_based=10
+time_based
rw=randtrim
numjobs=2
filename=fragmented_file
bs=4K
direct=0
numjobs=4
-time_based=1
+time_based
runtime=900
[file1]
bs=4K
direct=0
numjobs=1
-time_based=1
+time_based
runtime=900
[file1]
bs=4K
direct=0
numjobs=4
-time_based=1
+time_based
runtime=900
[file1]
bs=256K
direct=0
numjobs=4
-time_based=1
+time_based
runtime=900
[file1]
bs=256K
direct=1
numjobs=1
-time_based=1
+time_based
runtime=900
[file1]
bs=256K
direct=0
numjobs=1
-time_based=1
+time_based
runtime=900
[file1]
size=8g
ioengine=libpmem
norandommap
-time_based=1
+time_based
group_reporting
invalidate=1
disable_lat=1
bs=512K
direct=1
numjobs=16
-time_based=1
+time_based
runtime=300
[dev1]
size=100g
rw=randread
norandommap
-time_based=0
bs=1m
ioengine=pmemblk
norandommap
-time_based=1
+time_based
runtime=30
group_reporting
disable_lat=1
bs=512K
direct=1
numjobs=16
-time_based=1
+time_based
runtime=180
[dev1]