examples/libpmem.fio: clean up example
[fio.git] / examples / libpmem.fio
CommitLineData
ae0db592
TI
1[global]
2bs=4k
3size=8g
4ioengine=libpmem
5norandommap
6time_based=1
7group_reporting
8invalidate=1
9disable_lat=1
10disable_slat=1
11disable_clat=1
12clat_percentiles=0
13
14iodepth=1
15iodepth_batch=1
16thread=1
17numjobs=1
18
19#
20# In case of 'scramble_buffers=1', the source buffer
2057aedd 21# is rewritten with a random value every write operations.
ae0db592 22#
2057aedd
JA
23# But when 'scramble_buffers=0' is set, the source buffer isn't
24# rewritten. So it will be likely that the source buffer is in CPU
25# cache and it seems to be high performance.
ae0db592
TI
26#
27scramble_buffers=0
28
29#
30# direct=0:
31# Using pmem_memcpy_nodrain() for write operation
32#
33# direct=1:
34# Using pmem_memcpy_persist() for write operation
35#
36direct=0
37
38#
39# Setting for fio process's CPU Node and Memory Node
40#
41numa_cpu_nodes=0
42numa_mem_policy=bind:0
43
44#
45# split means that each job will get a unique CPU from the CPU set
46#
47cpus_allowed_policy=split
48
49#
50# The pmemblk engine does IO to files in a DAX-mounted filesystem.
51# The filesystem should be created on an NVDIMM (e.g /dev/pmem0)
52# and then mounted with the '-o dax' option. Note that the engine
53# accesses the underlying NVDIMM directly, bypassing the kernel block
54# layer, so the usual filesystem/disk performance monitoring tools such
55# as iostat will not provide useful data.
56#
57directory=/mnt/pmem0
58
59[libpmem-seqwrite]
60rw=write
61stonewall
62
63#[libpmem-seqread]
64#rw=read
65#stonewall
66
67#[libpmem-randwrite]
68#rw=randwrite
69#stonewall
70
71#[libpmem-randread]
72#rw=randread
73#stonewall