Last active
January 20, 2022 04:40
-
-
Save lukaszstolarczuk/b358293ad818447f0f0388161bbaa332 to your computer and use it in GitHub Desktop.
Example of FIO workload for libpmem engine
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# | |
# run command for this workload: | |
# numactl -N 0 fio LibpmemSeqR.fio # it binds this FIO workload to CPU 0 only. It should be set according to /dev/pmem6 socket's number | |
# | |
[global] | |
thread | |
group_reporting | |
norandommap | |
overwrite=1 | |
thinktime=0 | |
sync=0 | |
direct=0 | |
ioengine=libpmem | |
iodepth=1 | |
# | |
# Preparing namespace with commands: | |
# mkfs.ext4 /dev/pmem6 | |
# mount /dev/pmem6 /mnt/pmem6/ -o dax | |
# | |
directory=/mnt/pmem6 # I'm working on directory; each of 'numjobs' gets its own file to work with | |
size=50GB # Each file will have this size; so in summary they will fill the whole namespace | |
unlink=0 | |
time_based | |
runtime=300 | |
ramp_time=30 | |
[SeqRead] | |
bs=1M | |
numjobs=16 # depending on CPU core count more can be better, but also can be a bottleneck | |
rw=randrw | |
rwmixread=100 | |
percentage_random=0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Does the libpmem io engine support io depths other than 1?