Merge branch 'patch-1' of https://github.com/Nikratio/fio
[fio.git] / examples / libpmem.fio
... / ...
CommitLineData
1[global]
2bs=4k
3size=10g
4ioengine=libpmem
5norandommap
6time_based
7group_reporting
8invalidate=1
9disable_lat=1
10disable_slat=1
11disable_clat=1
12clat_percentiles=0
13
14iodepth=1
15iodepth_batch=1
16thread
17numjobs=1
18runtime=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#
25direct=1
26
27#
28# sync=1 means that pmem_drain() is executed for each write operation.
29#
30sync=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#
40scramble_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#
46numa_cpu_nodes=0
47numa_mem_policy=bind:0
48
49#
50# split means that each job will get a unique CPU from the CPU set
51#
52cpus_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
63directory=/mnt/pmem
64
65[libpmem-seqwrite]
66rw=write
67stonewall
68
69[libpmem-seqread]
70rw=read
71stonewall
72
73#[libpmem-randwrite]
74#rw=randwrite
75#stonewall
76
77#[libpmem-randread]
78#rw=randread
79#stonewall