Merge branch 'patch-1' of https://github.com/Nikratio/fio
[fio.git] / examples / libpmem.fio
1 [global]
2 bs=4k
3 size=10g
4 ioengine=libpmem
5 norandommap
6 time_based
7 group_reporting
8 invalidate=1
9 disable_lat=1
10 disable_slat=1
11 disable_clat=1
12 clat_percentiles=0
13
14 iodepth=1
15 iodepth_batch=1
16 thread
17 numjobs=1
18 runtime=300
19
20 #
21 # depends on direct option, flags are set for pmem_memcpy() call:
22 # direct=1 - PMEM_F_MEM_NONTEMPORAL,
23 # direct=0 - PMEM_F_MEM_TEMPORAL.
24 #
25 direct=1
26
27 #
28 # sync=1 means that pmem_drain() is executed for each write operation.
29 #
30 sync=1
31
32 #
33 # In case of 'scramble_buffers=1', the source buffer
34 # is rewritten with a random value every write operation.
35 #
36 # But when 'scramble_buffers=0' is set, the source buffer isn't
37 # rewritten. So it will be likely that the source buffer is in CPU
38 # cache and it seems to be high write performance.
39 #
40 scramble_buffers=1
41
42 #
43 # Setting for fio process's CPU Node and Memory Node.
44 # Set proper node below or use `numactl` command along with FIO.
45 #
46 numa_cpu_nodes=0
47 numa_mem_policy=bind:0
48
49 #
50 # split means that each job will get a unique CPU from the CPU set
51 #
52 cpus_allowed_policy=split
53
54 #
55 # The libpmem engine does IO to files in a DAX-mounted filesystem.
56 # The filesystem should be created on a Non-Volatile DIMM (e.g /dev/pmem0)
57 # and then mounted with the '-o dax' option.  Note that the engine
58 # accesses the underlying NVDIMM directly, bypassing the kernel block
59 # layer, so the usual filesystem/disk performance monitoring tools such
60 # as iostat will not provide useful data.
61 #
62 #filename=/mnt/pmem/somefile
63 directory=/mnt/pmem
64
65 [libpmem-seqwrite]
66 rw=write
67 stonewall
68
69 [libpmem-seqread]
70 rw=read
71 stonewall
72
73 #[libpmem-randwrite]
74 #rw=randwrite
75 #stonewall
76
77 #[libpmem-randread]
78 #rw=randread
79 #stonewall